On 15 Feb 2006 at 16:24, Waldek Hebisch wrote: [...]
With this data I can not give any specific advice. But generally in similar cases I use debugger just on original testcase. You need to start a debugger (say gdb) on the compiler proper (gpc1.exe) and give it correct arguments (running gpc -v will tell you which one). The debugger will (assuming that you have compiled your gpc with debugging support, which is a default) tell you offending line number and its file. In gdb typing `bt' will give you a backtrace (the whole call chain with arguments).
Unfortunately, running gpc1 directly (either in gdb or outside of it, with or without parameters) causes an ICE. "gpc -v" doesn't tell me how to run gpc1 correctly.
BTW. When testing gpc it us usefull to give `--enable-checking' option to `configure' -- the compiler build in such way performs extra internal checks (the checks make the compiler slower and larger, so they are disabled by default).
I will try this ...
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/