Thanks all for your replies!
@correa.elias: Well, I never experienced troubles with antivirus software. I can imagine antivirus interference if you... well, try to develop a virus...
@Thaddy:
Lazarus 1.8.4, FPC 3.0.4.
Windows 8.1 64 bit.
I can reproduce the SIGSEGV reliably by adding a break point to line 48, then go stepwise (by F7), receiving the SIGSEGV at line 37. The example program runs perfectly well (without SIGSEGV) if I run it without any break points. Maybe the debugger is causing this here?
In contrast to that my real application code leads to a freeze (even without a break point).
for what it's worth, I have an app that I started to develop using the 64 bit install. I have a thread in it that talks to serial ports and what happen a couple
of times when some actions went wrong in the thread while running the app under debug mode, it actually blue screened my Windows 10, something I have
never seen before..
The same app in the 32 bit install works fine while debugging if an error takes place in that code so I have continued to work on the project in the
32 bit mode for now and later I will compile a version of it in the 64 bit target.
Well, to be honest, from the example code I just get a SIGSEGV, nothing too bad.
If I do the same in my real application it fails by freezing my system. Although I'm not sure why this is, some low level libraries are loaded at this point and I think that this contributes to the worse behaviour.