This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: emacs and gdb


On Thu, Nov 6, 2008 at 12:15 PM, Andreas Schwab <schwab@suse.de> wrote:
> "Dave Milter" <davemilter@gmail.com> writes:
>
>> I met strange problem with running gdb under emacs,
>> I run it like this:
>> arm-eabi-gdb --annotate=3 someprog.elf
>> target remote :3333
>> Remote debugging using :3333
>> 0x00000004 in ?? ()
>> (gdb) monitor soft_reset_halt
>>
>> /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.
>>
>>
>> if I type the same commands in gdb running in terminal all ok:
>
> The Emacs frontend does a few things behind your back.  Those commands
> are issued with the server prefix so that they don't show up in the
> history.
>

But how can I find out what is going on? Is it possible to catch such commands,
for example force gdb to save them to file, without need to rebuild gdb?

I find out that
arm-eabi-gdb 6.6.50.20070821-cvs works fine under emacs 22.3.1
arm-eabi-gdb 6.8.50.20080706 give internal error above under emacs 22.3.1

so I almost sure that this is not emacs problem.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]