From: Holger Brunck <holger.brunck@keymile.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: Lukas Berk <lberk@redhat.com>, systemtap@sourceware.org
Subject: Re: print_ubacktrace() and ppc 32
Date: Tue, 18 Jun 2013 07:01:00 -0000 [thread overview]
Message-ID: <51C005AA.8010300@keymile.com> (raw)
In-Reply-To: <1371492348.4501.106.camel@bordewijk.wildebeest.org>
Hi,
On 06/17/2013 08:05 PM, Mark Wielaard wrote:
>> Unfortunately I believe this is because we don't actually support
>> > powerpc32 (only ppc64.h is defined in unwind.h). So while the first
>> > error you're getting is being worked on (I'm currently working on
>> > PR10272[1] so hopefully it'll be resloved soon), the second error will
>> > be the show stopper here.
> Yeah thanks. I had completely forgotten I only implemented the DWARF
> unwinder for ppc64. Sorry. This was because when I wrote the powerpc
> DWARF unwinder (kernel support) I only had access to ppc64 kernels.
>
ah ok thanks so it's currently unsupported.
> So for a ppc32 kernel we do need a new runtime/unwind/ppc32.h
> definitions file. It should not be that hard to write based on the
> ppc64.h version and the ppc32 DWARF register mappings from
> http://refspecs.linuxbase.org/elf/elfspec_ppc.pdf
> But note that testing might be needed to see if those really map to
> actually used DWARF register numbers generated by the toolchain. As can
> be seen in the comments in ppc64.h sometimes mistakes have been made and
> theory/spec and practice are not the same :{
Ok thanks for pointing out. If someone has a first ppc32.h file and needs
some help for testing on a native 32 bit ppc system, let me know. Or maybe
in the next week I find the time to implement one.
Best regards
Holger
next prev parent reply other threads:[~2013-06-18 7:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:24 Holger Brunck
2013-06-17 17:43 ` Mark Wielaard
2013-06-17 18:00 ` Lukas Berk
2013-06-17 18:05 ` Mark Wielaard
2013-06-18 7:01 ` Holger Brunck [this message]
2013-08-03 1:12 ` Lukas Berk
2013-08-05 8:46 ` Holger Brunck
2013-08-06 19:07 ` Lukas Berk
2013-08-07 7:16 ` Holger Brunck
2013-08-09 15:21 ` Lukas Berk
2013-08-12 8:58 ` Holger Brunck
2013-06-18 6:46 ` Holger Brunck
2013-06-17 17:46 ` David Smith
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=51C005AA.8010300@keymile.com \
--to=holger.brunck@keymile.com \
--cc=lberk@redhat.com \
--cc=mjw@redhat.com \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).