Re: wrong-code regressions review

[Bradley Lucier <lucier at math dot purdue dot edu>]

On Dec 15, 2004, at 4:29 PM, Daniel Jacobowitz wrote:

> On Wed, Dec 15, 2004 at 04:23:39PM -0500, Bradley Lucier wrote:
> > (gdb) info locals
> > ___pc = dwarf2_read_address: Corrupted DWARF expression.
>
> This is some new bug in GDB I haven't seen before.
>
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x081541ae in ___H__20___front (___ps=0x8481ea0) at _front.c:7075
> > 7075       ___SET_R2(___FIXMAX(___R3,___R2))
> > (gdb) info locals
> > ___pc = 137816529
> > ___start = 137799889
> > ___temp = Variable "___temp" is not available.
>
> This means GDB thinks it is in a call clobbered register.  It shouldn't
> happen in the topmost frame, so I don't know what's wrong.  I'd have to
> see the debug info.

After some more advice from Daniel, I've put the following information 
at

http://www.math.purdue.edu/~lucier/GNATS/GNATS-17

in the directories fomit-frame-pointer and fno-omit-frame-pointer.

gsc: the executable under x86-linux with

[lucier@cohomology gsc]$ uname -a
Linux cohomology 2.4.21-20.EL #1 Wed Aug 18 20:58:25 EDT 2004 i686 i686 
i386 GNU/Linux

fib.scm: the data that causes the executable to crash
_front.[iso]: The results from save-temps in the file where it crashes.
transcript: The transcript of the gdb sessions where these things 
happen, together with the compile lines.

Brad