From: "Dave Milter" <davemilter@gmail.com>
To: "Andreas Schwab" <schwab@suse.de>
Cc: gdb@sourceware.org
Subject: Re: emacs and gdb
Date: Thu, 06 Nov 2008 09:40:00 -0000 [thread overview]
Message-ID: <2a382c6e0811060139t324eb182h11400093efa65af5@mail.gmail.com> (raw)
In-Reply-To: <je3ai5b4fq.fsf@sykes.suse.de>
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.
next prev parent reply other threads:[~2008-11-06 9:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 7:07 Dave Milter
2008-11-06 9:16 ` Andreas Schwab
2008-11-06 9:40 ` Dave Milter [this message]
2008-11-06 9:44 ` Andreas Schwab
2008-11-06 10:31 ` Dave Milter
2009-01-25 1:17 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-11-23 2:36 Emacs and GDB a2782
2002-11-23 3:36 ` Eli Zaretskii
2002-11-23 3:59 ` a2782
2002-11-23 12:34 ` Eli Zaretskii
2002-11-23 15:52 ` Jim Blandy
2002-11-23 21:55 ` Eli Zaretskii
2002-11-25 6:50 ` Kris Warkentin
2002-12-05 16:56 ` Fernando Nasser
2002-12-09 9:40 ` a2782
2002-12-09 10:12 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2a382c6e0811060139t324eb182h11400093efa65af5@mail.gmail.com \
--to=davemilter@gmail.com \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox