From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, dave.anglin@nrc-cnrc.gc.ca,
carlos@systemhalted.org
Subject: Re: parisc: unwind tables and backtraces broken?
Date: Tue, 07 Jul 2009 11:07:14 +0800 [thread overview]
Message-ID: <4A52BBE2.7020507@tausq.org> (raw)
In-Reply-To: <20090707005018.C697F4FE0@hiauly1.hia.nrc.ca>
John David Anglin wrote:
>> I started looking into why CONFIG_BACKTRACE_SELF_TEST=y shows uncomplete/wrong/broken backtraces.
>>
>> To me it seems, that the unwind tables are broken when using newer gcc/binutils versions.
>
> Just wondering, but would it be possible to switch to using dwarf2 unwind
> information. I presume that's what most other targets use.
the hppa kernel unwinder is derived from the ia64 unwinder, which is not
dwarf2 based.
The only dwarf references I find in the kernel are some dwarf markups in
signal frames to help userspace with signal frame unwinding. Have I
missed anything?
x86 seems to do something very ad-hoc.
randolph
next prev parent reply other threads:[~2009-07-07 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 21:58 parisc: unwind tables and backtraces broken? Helge Deller
2009-07-07 0:50 ` John David Anglin
2009-07-07 3:07 ` Randolph Chung [this message]
2009-07-07 4:42 ` Kyle McMartin
2009-07-07 14:07 ` Carlos O'Donell
2009-07-07 18:02 ` Helge Deller
2009-07-07 2:57 ` Randolph Chung
2009-07-07 18:01 ` Helge Deller
2009-07-07 18:33 ` John David Anglin
2009-07-07 20:36 ` Carlos O'Donell
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=4A52BBE2.7020507@tausq.org \
--to=randolph@tausq.org \
--cc=carlos@systemhalted.org \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.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