public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: Holger Brunck <holger.brunck@keymile.com>
Cc: systemtap@sourceware.org
Subject: Re: print_ubacktrace() 	 and ppc 32
Date: Mon, 17 Jun 2013 17:43:00 -0000	[thread overview]
Message-ID: <1371491014.4501.97.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <51BF1C1E.7020208@keymile.com>

On Mon, 2013-06-17 at 16:24 +0200, Holger Brunck wrote:
> I am using systemtap userspace probes on a 32-Bit powerpc architecture. I do
> crosscompile the probes on a 64-Bit x86 host.
> 
> The version I use is:
> Systemtap translator/driver (version 2.3/0.152, non-git sources)
> 
> If I use print_ubacktrace() in my stap script it won't compile. I am getting two
> main error messages and I ask myself which one tells me the real reason for the
> error:
> 
> backtraces for 32bit programs on 64bit kernels don't work.

Yes, if your powerpc kernel is 64bit, but the user program is 32bit
(same for 32bit user space on x86_64) then you will get that warning
during stap translation time (the stap script should still run, but
won't produce a user backtrace for the 32bit module/library/process).
This is bug: http://sourceware.org/bugzilla/show_bug.cgi?id=10272
"backtraces fail with 32-on-64 executables"

> systemtap-2.3-32645/share/systemtap/runtime/stack.c:85:2: error: #error
> "Unsupported architecture"

This might be caused by the cross compiling, maybe something got
confused about the architecture. You get that when:
#ifndef STP_USE_DWARF_UNWINDER
powerpc (and x86_64) both should use the DWARF_UNWINDER. So you might
want to look at why that doesn't get defined in your case.

Cheers,

Mark

  reply	other threads:[~2013-06-17 17:43 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 [this message]
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
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=1371491014.4501.97.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=holger.brunck@keymile.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).