This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: emacs and gdb
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: "Dave Milter" <davemilter at gmail dot com>
- Cc: "Andreas Schwab" <schwab at suse dot de>, gdb at sourceware dot org
- Date: Sun, 25 Jan 2009 14:17:01 +1300
- Subject: Re: emacs and gdb
- References: <2a382c6e0811052307r6ae0510ewf5569f59c93446a6@mail.gmail.com> <je3ai5b4fq.fsf@sykes.suse.de> <2a382c6e0811060139t324eb182h11400093efa65af5@mail.gmail.com> <jeprl99ok6.fsf@sykes.suse.de> <2a382c6e0811060231n58f95a98u375068098d818ba7@mail.gmail.com>
> (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