From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-33282-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 19491 invoked by alias); 6 Nov 2008 09:40:35 -0000
Received: (qmail 19423 invoked by uid 22791); 6 Nov 2008 09:40:35 -0000
X-Spam-Check-By: sourceware.org
Received: from wa-out-1112.google.com (HELO wa-out-1112.google.com) (209.85.146.177)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 06 Nov 2008 09:39:51 +0000
Received: by wa-out-1112.google.com with SMTP id v33so290485wah.24         for <gdb@sourceware.org>; Thu, 06 Nov 2008 01:39:49 -0800 (PST)
Received: by 10.114.79.18 with SMTP id c18mr527872wab.215.1225964389352;         Thu, 06 Nov 2008 01:39:49 -0800 (PST)
Received: by 10.114.180.15 with HTTP; Thu, 6 Nov 2008 01:39:49 -0800 (PST)
Message-ID: <2a382c6e0811060139t324eb182h11400093efa65af5@mail.gmail.com>
Date: Thu, 06 Nov 2008 09:40:00 -0000
From: "Dave Milter" <davemilter@gmail.com>
To: "Andreas Schwab" <schwab@suse.de>
Subject: Re: emacs and gdb
Cc: gdb@sourceware.org
In-Reply-To: <je3ai5b4fq.fsf@sykes.suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2a382c6e0811052307r6ae0510ewf5569f59c93446a6@mail.gmail.com> 	 <je3ai5b4fq.fsf@sykes.suse.de>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-11/txt/msg00047.txt.bz2

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.