This is 2 decade of development (and for 19 years worked flawlessly) - and in the last 6 months, the windows build is broken. Not sure if it is a 3.0.4 FPC issue, or, a change in the 3.x builds - that I am unaware of.
On Sat, Sep 28, 2019 at 3:19 PM Alexander Grotewohl <a...@dcclost.com> wrote: > or maybe don't use the variable name "result" because it might point to > the special delphi "result" var and not yours? > > -- > Alexander Grotewohl > http://dcclost.com > > On Sep 28, 2019 4:15 PM, Alexander Grotewohl <a...@dcclost.com> wrote: > > don't know off the top of my head but does the ord() bit segfault without > assigning it to anything? like if the function only had writleln(ord())! or > does the result:= section segfault using ord() without the pointers? > > my guess is it works on linux/mac purely by luck. but i could be wrong. > > -- > Alexander Grotewohl > http://dcclost.com > > On Sep 28, 2019 3: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 - firstname.lastname@example.org > https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel >
_______________________________________________ fpc-devel maillist - email@example.com https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel