Okay, so I see no other way out than remote debugging ... :-(
I pulled in a binary of gdb this morning, but (probably since I'm not familiar with it) I didn't get anything useful out of that. I examined the core with the aix debugger and this is what I see with the command "where" (this command shows where the program stops). Output is below (ignore the "= internal error" parts, they originate from the fact that the aix debugger does not understand everything that gcc added in the gpc1 executable).
---begin--- [using memory image in core]
IOT/Abort trap in raise at 0xd0077eac 0xd0077eac (raise+0x20) 80410014 lwz r2,0x14(r1) (dbx) where raise(??) at 0xd0077eac abort() at 0xd0019a70 unnamed block $b2307, line 4027 in "rs6000.c" output_epilog(??, ??), line 4027 in "rs6000.c" final_end_function(??, ??, ??), line 1151 in "final.c" rest_of_compilation(decl = internal error: assertion failed at line 947 in file frame.c 0x20080a2c), line 3647 in "toplev.c" finish_function(??), line 8734 in "gpc-decl.c" yyparse(), line 6628 in "parse.y" compile_file(name = internal error: assertion failed at line 947 in file frame.c
(nil)), line 2494 in "toplev.c" main(argc = 15, argv = 0x2ff227cc, envp = 0xffffffff), line 4377 in "toplev.c" ---end---
So what do we learn from that?........
Nick
P.S. when replying to the list please cc to me (cremelie@elis.rug.ac.be)