From: Joel Brobecker <brobecker@adacore.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Infinite backtraces...
Date: Fri, 03 Dec 2004 18:49:00 -0000 [thread overview]
Message-ID: <20041203184903.GH16491@adacore.com> (raw)
In-Reply-To: <41B0AFED.5050803@gnu.org>
> I've a finish up a patch that checks for this:
> > #6 0x7aee0f08 in __pthread_create_system () from /usr/lib/libpthread.1
> > #7 0x00000000 in ?? ()
> I.e., a zero pc unwound from a normal frame. It is ``tricky'' to test
> though :-(
That's pretty much what I have done as a proof of concept.
I ran it through the testsuite on our HP machine, and we got
3 new passes (from 3 unresolved, due to the expect buffer filling up).
> The other thing that would help here is for glibc's CFI to identify the
> return-address (and CFA) column as unknown (assuming I've got my CFI
> term correct) on the outer most frame. It would then be easy for
> dwarf2-unwind to identify this. It's been discussed, agreed, but not
> implemented.
This is of course a good solution, provided that you can use dwarf2.
On 32bit HP/UX, we're stuck.
> Right, but it shouldn't need an additional method. The per-architecture
> unwinder, when it detects a frame that the ABI specifies as final,
> should return a null frame ID. For instance, the PPC ABI explicitly
> specifies that it's stack be terminated with a zero SP.
I am not sure this is doable. Is it? Let me check that again. Perhaps
it's ok to create the frame object, but then later compute a null frame
ID for it? As far as I remember, the sequence of events is like this
when trying to build the frame chain:
. get_prev_frame (this_frame):
. get_frame_id (this_frame)
. frame_id (next_frame, this_cache)
. check this frame ID
. build previous frame
(frame ID unset)
And then, after building each new frame, we display the information
for that new frame.
> Finally, a more long term suggestion is that we add a mechanism for
> creating or adding attributes to symbols (for instance for signal
> trampolines). An atribute of such a symbol could be that it is
> outermost.
But could we determine that a symbol is outermost. And couldn't the
same symbol be used in both contexts?
--
Joel
next prev parent reply other threads:[~2004-12-03 18:49 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
2004-12-03 18:28 ` Andrew Cagney
2004-12-03 18:49 ` Joel Brobecker [this message]
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=20041203184903.GH16491@adacore.com \
--to=brobecker@adacore.com \
--cc=cagney@gnu.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