From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc, frame] Add backtrace stop reasons
Date: Mon, 21 Aug 2006 12:50:00 -0000 [thread overview]
Message-ID: <20060820165007.GC20987@nevyn.them.org> (raw)
In-Reply-To: <200608201438.k7KEcJho022644@elgar.sibelius.xs4all.nl>
On Sun, Aug 20, 2006 at 04:38:19PM +0200, Mark Kettenis wrote:
> > Any comments on this patch? It doesn't have any major change on GDB's
> > visible behavior; it changes one error to a printf, but that error was
> > always wrapped in a catch_exceptions anyway, so this is unimportant.
> > The text of the message on a corrupt stack is changed mildly; it says
> > "Backtrace stopped: previous..." rather than just "Previous...".
>
> That's a useful clarification I think.
Oh, here's another thing which I think is useful: you'll get the
"Backtrace stopped" message every time you say backtrace, but you used
to only get the Previous... error the first time, which I always found
somewhat confusing. That's because we cached the failure, but not the
failure reason.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-20 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 13:02 Daniel Jacobowitz
2006-08-20 16:50 ` Mark Kettenis
2006-08-20 17:05 ` Daniel Jacobowitz
2006-08-22 20:24 ` Mark Kettenis
2006-08-22 20:38 ` Daniel Jacobowitz
2006-08-22 20:49 ` Mark Kettenis
2006-08-22 20:58 ` Daniel Jacobowitz
2006-10-05 22:33 ` Daniel Jacobowitz
2006-10-18 19:52 ` Daniel Jacobowitz
2006-08-21 12:50 ` Daniel Jacobowitz [this message]
2006-08-22 20:41 ` Mark Kettenis
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=20060820165007.GC20987@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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