emacs and gdb
Nick Roberts
nickrob@snap.net.nz
Sun Jan 25 01:17:00 GMT 2009
> (gdb) target remote :3333
> Remote debugging using :3333
> 0x00000004 in ?? ()
> (gdb) info frame
> Cannot access memory at address 0xffe7fdff
> Stack level 0, frame at 0x0:
> pc = 0x4; saved pc
> /home/test/src/toolchains/gdb/gdb-6.8.50.20080706/gdb/findvar.c:298:
> 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.
>
> emacs call info frame, and this cause gdb failure,
> is this gdb bug?
Yes, I think this is a gdb bug and I have filed a bug report here:
http://sourceware.org/bugzilla/show_bug.cgi?id=9786
--
Nick http://www.inet.net.nz/~nickrob
More information about the Gdb
mailing list