From: Daniel Jacobowitz <drow@false.org>
To: "Zarges, Olav" <Olav.Zarges@imc-berlin.de>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb-6.5 produces infinite backtrace on ARM
Date: Mon, 21 Aug 2006 12:42:00 -0000 [thread overview]
Message-ID: <20060821124241.GA16416@nevyn.them.org> (raw)
In-Reply-To: <44E999B4.5030905@imc-berlin.de>
On Mon, Aug 21, 2006 at 01:32:04PM +0200, Zarges, Olav wrote:
> Sounds pretty good. Good job! I can't wait to lay my hands on the patch...
>
> Another question arose from you answer: what is a gdb/mi front-end supposed
> to do when a message like
>
> "Backtrace stopped: frame did not save the PC" or
> "Previous frame identical to this frame (corrupt stack?)" or
> ...
>
> is returned at the end of the backtrace? Eclipse just throws away the
> complete backtrace for the corresponding thread.
What other versions of GDB are you looking at? With older versions, it was an
^error; with newer it's a ~"console output message". I would not
expect Eclipse to throw away the backtrace if there's a console output
message.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-21 12:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 8:15 Zarges, Olav
2006-08-15 12:41 ` Daniel Jacobowitz
2006-08-15 13:54 ` Zarges, Olav
2006-08-19 5:24 ` Daniel Jacobowitz
2006-08-21 11:35 ` Zarges, Olav
2006-08-21 12:42 ` Daniel Jacobowitz [this message]
2006-08-21 14:37 ` Zarges, Olav
2006-08-21 14:54 ` Daniel Jacobowitz
2006-09-06 13:32 ` Zarges, Olav
2006-09-06 14:44 ` Daniel Jacobowitz
2006-09-06 15:03 ` Zarges, Olav
2006-09-06 15:19 ` Daniel Jacobowitz
2006-09-06 15:38 ` Zarges, Olav
2006-09-06 15:52 ` Daniel Jacobowitz
2006-09-07 16:15 ` Zarges, Olav
2006-09-07 17:38 ` Daniel Jacobowitz
2006-09-10 14:49 ` Daniel Jacobowitz
2006-09-19 1:40 ` Michael Snyder
2006-09-19 3:17 ` Daniel Jacobowitz
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=20060821124241.GA16416@nevyn.them.org \
--to=drow@false.org \
--cc=Olav.Zarges@imc-berlin.de \
--cc=gdb@sourceware.org \
/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