This is the mail archive of the
mailing list for the GDB project.
Re: emacs and gdb
On Thu, Nov 6, 2008 at 12:44 PM, Andreas Schwab <email@example.com> wrote:
> "Dave Milter" <firstname.lastname@example.org> writes:
>> But how can I find out what is going on? Is it possible to catch such commands,
> Try to set gdb-server-prefix to "".
>> for example force gdb to save them to file, without need to rebuild gdb?
> Try "set logging on".
Thanks a lot, I got this, at now gdb running in terminal:
(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
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?