From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc, frame] Add backtrace stop reasons
Date: Thu, 05 Oct 2006 22:33:00 -0000 [thread overview]
Message-ID: <20061005223335.GD14087@nevyn.them.org> (raw)
In-Reply-To: <20060822204131.GA31802@nevyn.them.org>
On Tue, Aug 22, 2006 at 04:41:31PM -0400, Daniel Jacobowitz wrote:
> On Tue, Aug 22, 2006 at 10:37:53PM +0200, Mark Kettenis wrote:
> > Perhaps you should post that updated patch!
>
> Sure; here it is.
> 2006-08-19 Daniel Jacobowitz <dan@codesourcery.com>
>
> * frame.c (struct frame_info): Add stop_reason.
> (get_prev_frame_1): Set stop_reason. Don't call error for
> stop reasons.
> (get_frame_unwind_stop_reason, frame_stop_reason_string): New.
> * frame.h (enum unwind_stop_reason): New.
> (get_frame_unwind_stop_reason, frame_stop_reason_string): New
> prototypes.
> * stack.c (frame_info): Print the stop reason.
> (backtrace_command_1): Print the stop reason for errors.
Mark, I believe you were happy with this version of the patch; is that
right? No one else commented, so if you think it's OK, I will check it
in.
The second patch from this group of three definitely requires more
discussion, but the third was pretty clear-cut, and Michael reminded
me that I hadn't gotten back to it. It could be untangled from this
one, but if this is OK, I'd rather put it in first.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-05 22:33 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 [this message]
2006-10-18 19:52 ` Daniel Jacobowitz
2006-08-21 12:50 ` Daniel Jacobowitz
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=20061005223335.GD14087@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