gdb crash under emacs in fedora11

gdb crash under emacs in fedora11

[David L]

When I run gdb under emacs and attach to a gdbserver session,
I get an error like this:

A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y
../../gdb/findvar.c:300: internal-error: value_of_register_lazy:
Assertion `frame_id_p (get_frame_id (frame))' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y

It seems to only happen when I run under emacs and use gdbserver,
so I don't know if it's a gdb problem or an emacs problem.  But
installing emacs from cvs instead of using the version that
comes with fedora11 fixes the problem.  Any thoughts on whether this
is an emacs bug, a gdb bug, a gdbserver bug or what?  It's odd
that I only get the error when using all three.

Cheers,

                David

gdb crash under emacs in fedora11

[Nick Roberts]

David L writes:
 > When I run gdb under emacs and attach to a gdbserver session,
 > I get an error like this:
 > 
 > A problem internal to GDB has been detected,
 > further debugging may prove unreliable.
 > Quit this debugging session? (y or n) y
 > ../../gdb/findvar.c:300: internal-error: value_of_register_lazy:
 > Assertion `frame_id_p (get_frame_id (frame))' failed.
 > A problem internal to GDB has been detected,
 > further debugging may prove unreliable.
 > Create a core file of GDB? (y or n) y

This is a bug with current GDB that I have reported:

http://sourceware.org/bugzilla/show_bug.cgi?id=9786

(The connection with Emacs is that it issues "info frame" behind the
users back).  I've added it as something that needs to be fixed before
the next release (7.0) at:

http://sourceware.org/gdb/wiki/GDB_7.0_Release

It don't think it happens with GDB 6.7, or earlier, and, while I see it in
32 bit x86 GNU/Linux, it doesn't appear to happen in 64 bit.

-- 
Nick                                           http://www.inet.net.nz/~nickrob