public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Lukas Berk <lberk@redhat.com>
To: Holger Brunck <holger.brunck@keymile.com>
Cc: Mark Wielaard <mjw@redhat.com>, systemtap@sourceware.org
Subject: Re: print_ubacktrace()   and ppc 32
Date: Sat, 03 Aug 2013 01:12:00 -0000	[thread overview]
Message-ID: <20130803011202.GA1956@redhat.com> (raw)
In-Reply-To: <51C005AA.8010300@keymile.com>


[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]

Hey,

> > 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.

Looking over the DWARF register specs the mappings should be the same,
so hopefully we can use the same header file.  Would you mind trying
this patch?

Cheers,

Lukas

[-- Attachment #1.2: ppc32.patch --]
[-- Type: text/plain, Size: 417 bytes --]

diff --git a/runtime/unwind/unwind.h b/runtime/unwind/unwind.h
index 056b539..7a4fab8 100644
--- a/runtime/unwind/unwind.h
+++ b/runtime/unwind/unwind.h
@@ -23,7 +23,7 @@ struct unwind_frame_info
 #include "x86_64.h"
 #elif  defined (__i386__)
 #include "i386.h"
-#elif defined (__powerpc64__)
+#elif defined (__powerpc64__) || defined (__powerpc__)
 #include "ppc64.h"
 #elif defined (__s390x__)
 #include "s390x.h"

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-03  1:12 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
2013-08-03  1:12         ` Lukas Berk [this message]
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=20130803011202.GA1956@redhat.com \
    --to=lberk@redhat.com \
    --cc=holger.brunck@keymile.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).