According to Bernhard Tschirren:

Every time I compiled my programs with "-g" (debugging) the compiler crashed with a SIGSEGV. With a bit of late-night detective-ing, I think I figured WHY this happens!

I managed to get an assembly dump of my program without the compiler crashing. The "-g" option wrote ".def _(null) ... " to the assembly output. Somehow, some NULL strings have crept into GPC.... :-( Whats even scarier is that the number of _(null) defs varied between different compiles!

That's a good hint for what kind of errors to look out; however it's hopeless to check all 2MB of GPC source code for NULL pointer dereferences ... ;-) and my own test programs are compiled with `-g -O3 -Wall' all the time. Could you please mail me a short test program which triggers the bug?

Thanks in advance,

Peter

Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski@uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201] maintainer GNU Pascal [970510] - http://home.pages.de/~gnu-pascal/ [970125]