Adriaan van Os dixit:
Thorsten Glaser wrote:
Adriaan van Os dixit:
Well, you can see what gdb tells you.
My gdb skills are limited...
Program received signal SIGSEGV, Segmentation fault. 0x08248b92 in _p_Write_String () from /usr/lib/libgpc.so.2.1 Current language: auto; currently c (gdb) bt #0 0x08248b92 in _p_Write_String () from /usr/lib/libgpc.so.2.1 #1 0x1c0009ea in main program () at ./mir047h.pas:41 #2 0x1c000ab3 in main (argc=1, argv=0xcfbf12d0, envp=0xcfbf12d8) at <implicit code>:43
This is weird, because the testsuite indicated a bus error, rather than a
No, that was on i386. It's been easier for me to test on my local box than to ssh to the Macintosh again ;)
segmentation fault (as if the bus error was caused by an exception handler that is now intercepted by gdb). It could be a stack problem.
There were no unexpected testsuite failures.
Interesting. So it might be something else after all. Any gdb wizard here? I've only ever used DEBUG.COM and Borland's Turbo Debugger 1.0 for DOS in the past...
But I don't know if the stack detector automatically also works for Pascal (maybe Waldek can say).
I disabled it for Ada because they have their own system (which even conflicts with it), but didn't do it (yet) for Pascal, because I don't know if it can catch some (corner?) cases which the integrated checks (like {$R+,S+} etc.) don't find. I'm waiting for a response from the GPC wizards regarding this ;)
On a side note, ProPolice was redesigned and then integrated into gcc 4.1, so for the gpc port to gcc4 this might be interesting too.
bye, //mirabile