From: Randolph Chung <randolph@tausq.org>
To: gdb-patches@sources.redhat.com
Subject: [patch/rfa] allow unwinding "past main" for dummy frames
Date: Mon, 06 Dec 2004 03:31:00 -0000 [thread overview]
Message-ID: <20041206032726.GB6359@tausq.org> (raw)
On hpux, we push a small bit of code on the stack to implement function
calls from gdb. The stack trampoline contains a return address that
points back to the current function. this is needed to properly restore
the space registers (see hppa_hpux_push_dummy_code in hppa-hpux-tdep.c
for a much more detailed explanation). The upshot of all of this is
that when we do a backtrace from a gdb-called function, a backtrace can
be prematurely truncated at a dummy frame. Since it doesn't make sense
anyway to stop unwinding at dummy frames, this patch skips the "main
function" detection logic for dummy frames. The same logic is already
there for checking against the entry function a bit farther down in
get_prev_frame ().
ok?
randolph
2004-12-05 Randolph Chung <tausq@debian.org>
* frame.c (get_prev_frame): Don't terminate unwinding at main if we
are unwinding through a dummy frame.
Index: frame.c
===================================================================
RCS file: /cvs/src/src/gdb/frame.c,v
retrieving revision 1.195
diff -u -p -r1.195 frame.c
--- frame.c 10 Nov 2004 23:26:33 -0000 1.195
+++ frame.c 6 Dec 2004 03:19:46 -0000
@@ -1200,6 +1200,7 @@ get_prev_frame (struct frame_info *this_
gdb_assert (this_frame != NULL);
if (this_frame->level >= 0
+ && get_frame_type (this_frame) != DUMMY_FRAME
&& !backtrace_past_main
&& inside_main_func (this_frame))
/* Don't unwind past main(). Note, this is done _before_ the
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next reply other threads:[~2004-12-06 3:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 3:31 Randolph Chung [this message]
2004-12-06 3:45 ` Daniel Jacobowitz
2004-12-06 4:27 ` Randolph Chung
2004-12-06 4:59 ` Daniel Jacobowitz
2004-12-06 6:22 ` Randolph Chung
2004-12-06 15:35 ` Daniel Jacobowitz
2004-12-06 16:54 ` Randolph Chung
2004-12-08 3:27 ` Randolph Chung
2004-12-06 14:11 ` Randolph Chung
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=20041206032726.GB6359@tausq.org \
--to=randolph@tausq.org \
--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