From: Daniel Jacobowitz <drow@false.org>
To: Robert Norton <rnorton@broadcom.com>
Cc: gdb@sourceware.org
Subject: Re: Target Dependent Backtrace Termination
Date: Tue, 12 Jun 2007 12:05:00 -0000 [thread overview]
Message-ID: <20070612120544.GA31806@caradoc.them.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C01B3569E@NT-IRVA-0752.brcm.ad.broadcom.com>
On Tue, Jun 12, 2007 at 04:56:57AM -0700, Robert Norton wrote:
> I think this would be a good idea. I was certainly confused for a while
> because of this, and given the recent discussion on this list about the
> importance of unique frame IDs not having any for the outermost frame
> seems like a bad idea. If you're not keen to add a field to struct
> frame_id or change the signature of frame_this_id, perhaps
> get_prev_frame_1 could be more eager about getting the frame id for the
> prev frame then if it turns out to be null return null to indicate no
> previous frame? This is how I assumed things would work given the
> current interface.
No, I think it would be wiser to do one of the other two ideas you
mentioned. Minimizing unwinding is the central tenet of our current
design, and it seems to work well (though we have room to do it
better).
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-06-12 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 9:23 Robert Norton
2007-06-12 11:22 ` Daniel Jacobowitz
2007-06-12 11:57 ` Robert Norton
2007-06-12 12:05 ` Daniel Jacobowitz [this message]
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=20070612120544.GA31806@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rnorton@broadcom.com \
/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