From: Joel Brobecker <brobecker@adacore.com>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Infinite backtraces...
Date: Tue, 07 Dec 2004 09:40:00 -0000 [thread overview]
Message-ID: <20041206182914.GC1492@adacore.com> (raw)
In-Reply-To: <20041206035112.GE6359@tausq.org>
> #0 callee
> #1 callee stub
> #2 caller
>
> if you do a "finish" from callee, gdb will stop in the callee stub
> instead of at the caller. quite annoying :(
Ah yes, of course. What a bummer.
> i'm wondering if we should make the hppa unwinders more export-stub
> aware -- e.g. in hppa_frame_cache (), after we've determined the address
> of the current frame, we can see if this is an "export stub" frame, and
> if so automatically rewind one more frame. i think this should work and
> shouldn't cause any problems.... thoughts?
I would certainly agree with that.
--
Joel
next prev parent reply other threads:[~2004-12-07 9:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:46 Joel Brobecker
2004-12-02 23:13 ` Joel Brobecker
2004-12-03 2:43 ` Randolph Chung
2004-12-03 2:57 ` Joel Brobecker
2004-12-03 4:53 ` Randolph Chung
2004-12-03 19:36 ` Joel Brobecker
2004-12-03 18:03 ` Randolph Chung
2004-12-03 18:20 ` Joel Brobecker
2004-12-03 18:22 ` Randolph Chung
2004-12-06 7:25 ` Randolph Chung
2004-12-07 10:07 ` Joel Brobecker
2004-12-07 16:31 ` Randolph Chung
2004-12-07 16:37 ` Joel Brobecker
2004-12-07 16:52 ` Randolph Chung
2004-12-08 1:51 ` Randolph Chung
2004-12-12 16:36 ` [commit] Move zero PC check to frame.c; Was: " Andrew Cagney
2004-12-03 18:22 ` Joel Brobecker
2004-12-06 4:15 ` Randolph Chung
2004-12-07 9:40 ` Joel Brobecker [this message]
2004-12-03 18:28 ` Andrew Cagney
2004-12-03 18:49 ` Joel Brobecker
2004-12-03 19:26 ` Andrew Cagney
2004-12-03 20:19 ` Joel Brobecker
2004-12-03 21:44 ` Andrew Cagney
2004-12-03 22:16 ` Joel Brobecker
2004-12-03 22:23 ` Daniel Jacobowitz
2004-12-03 22:25 ` Joel Brobecker
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=20041206182914.GC1492@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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