This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-19980508 powerpc-ibm-aix4.1.4.0 results (failures with -p/-pg)
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: egcs-19980508 powerpc-ibm-aix4.1.4.0 results (failures with -p/-pg)
- From: Jeffrey A Law <law at hurl dot cygnus dot com>
- Date: Sat, 16 Jan 1999 21:31:01 -0700
- cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, egcs at cygnus dot com, meissner at cygnus dot com
- Reply-To: law at cygnus dot com
In message <9901170417.AA85680@marc.watson.ibm.com>you write:
> mr 31,11
> lwz 9,0(31)
> mtctr 9
> lwz 0,8(31)
> lwz 1,12(31) <--- dies here
> stw 0,0(1)
> lwz 11,LC..0(2)
> bctr
>
> (gdb) x/4x $r31
> 0x100004cc <y+96>: 0x60000000 0x7fc3f378 0x7fa4eb78 0x7f85e378
> (gdb) print/x $r9
> $30 = 0x60000000
> (gdb) print/x $r0
> $31 = 0x7fa4eb78
> (gdb) print/x $r1
> $32 = 0x2ff08ef0
> (gdb) stepi
>
> Program terminated with signal SIGKILL, Killed.
> The program no longer exists.
Weird. Real weird.
If you have an interest in tracking this down, you might try something like
inserting an instruction you know will cause a core dump just before the
stw and see if you get a valid core dump.
Another possibility is to put a break instruction before the stw and not use
stepi. There may be weird things that happen with stepi that we don't know
about.
Trying IBM's debuggers might prove useful too.
Just thoughts. This kind of stuff is a bear to track down.
jeff