[image: image.png]
Okay, getting better at FPC.EXE debugging... it appears, that 3.0.4 (or
Windows) passing a Const Pointer is handled differently?

* The bottom grey line - shows RES = xD9020, however, the
LapeOrdChar(show's it's 2nd parameter as 0x0 instead of xD9020). I was
originally focusing on Params^[0] - but that is not the error -
Result:Pointer is wrong address - even though the calling convention passed
in the correct address.  ** Again, this is only broken on my Windows
compile. I use 2.6.4 on Linux 64bit, and 3.0.4 on Mac (which works) and on
Windows. Same compile options (I compile via CLI).


On Sat, Sep 28, 2019 at 2:21 PM Ozz Nixon <ozzni...@gmail.com> wrote:

> [image: image.png]
> When I evaluate the code - it is perfect. However, when I run the code, it
> raises a SIGSEGV - Segmentation fault. Yet, the code runs perfectly on
> Linux 64bit machine, and Mac 32bit.
fpc-devel maillist  -  fpc-devel@lists.freepascal.org

Reply via email to