From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Mostly kill FRAME_CHAIN_VALID, add user knob
Date: Fri, 10 Jan 2003 20:10:00 -0000 [thread overview]
Message-ID: <3E1F28BB.9080704@redhat.com> (raw)
In-Reply-To: <20021226191541.GA8483@nevyn.them.org>
FYI, on the unwind branch, I'm adding the below to get_prev_frame()
/* There is always a frame. If this assertion fails, suspect that
something should be calling get_selected_frame() or
get_current_frame(). */
gdb_assert (next_frame != NULL);
if (next_frame->level >= 0
/* && !backtrace_below_main */
&& inside_main_func (next_frame->pc))
/* Don't unwind past main(), always unwind the sentinel frame.
Note, this is done _before_ the frame has been marked as
previously unwound. That way if the user later decides to
allow unwinds past main(), it can just happen. */
return 0;
/* Only try to do the unwind once. */
if (next_frame->prev_p)
return next_frame->prev;
next_frame->prev_p = 1;
Should eliminate that need to flush the frame cache everytime that
command is issued (should be able to merge it into current code as well).
Looking at the other checks:
/* If we're already inside the entry function for the main objfile,
then it isn't valid. */
if (inside_entry_func (get_frame_pc (fi)))
return 0;
I'd better add that one as well (but, I think, after ->prev_p). Note
that this and the test below do the same thing, so only one is needed.
It is just that one stops things a frame later.
/* If we're inside the entry file, it isn't valid. */
/* NOTE/drow 2002-12-25: should there be a way to disable this check?
it assumes a single small entry file, and the way some debug readers
(e.g. dbxread) figure out which object is the entry file is somewhat
hokey. */
if (inside_entry_file (frame_pc_unwind (fi)))
return 0;
Should this one be dropped? If the user specified unwind past main,
then they problably want _start() included in the backtrace. It's
presence also makes the other inside_entry_file() test redundant.
Andrew
PS: The command/variable should be `backtrace-*above*-main', or perhaphs
`backtrace-before-main' (before ~= prev).
next prev parent reply other threads:[~2003-01-10 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 12:20 Daniel Jacobowitz
2003-01-02 19:34 ` Andrew Cagney
2003-01-05 1:42 ` Daniel Jacobowitz
2003-01-05 1:44 ` Daniel Jacobowitz
2003-01-06 23:03 ` Andrew Cagney
2003-01-10 20:10 ` Andrew Cagney [this message]
2003-01-10 20:29 ` Andrew Cagney
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=3E1F28BB.9080704@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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