public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: Zhiwei Ying <zhiwei.ying@gmail.com>
Cc: systemtap <systemtap@sources.redhat.com>
Subject: Re: cannot trace user-level code in cross compilation environment
Date: Fri, 01 Apr 2011 18:25:00 -0000	[thread overview]
Message-ID: <4D961887.3000200@redhat.com> (raw)
In-Reply-To: <AANLkTin4+Q1r4j1LBKhv-x5-wXYf5CvryNTbOt3x71N1@mail.gmail.com>

On 04/01/2011 02:05 AM, Zhiwei Ying wrote:
> Hi,
> 
> I built a systemtap1.4 on ubuntu 10.4 32 bits. And also cross-compile
> staprun to a develop board with kernel 2.6.35 x86.
> 
> On the host pc side,
> 
> stap -r /target-board/kernel xxx.stp -p 4 -m traceauto.ko
> 
> then copy the traceauto.ko to the board,
> staprun -u -v -m traceauto.ko -c ./hello
> 
> 
> xxx.stp
> probe process("/ddtv/tracedrv/test/dhg/hello/hello").function("*").call

Is your "hello" binary at the same path on the host and target?  The
runtime looks for probe targets based on the path, so it will never
notice if the application is started from a different path.

There's a bug open to address this, but for now the only workaround is
to copy or link the binary to matching locations on the host and target.
http://sourceware.org/bugzilla/show_bug.cgi?id=12331

Josh

  parent reply	other threads:[~2011-04-01 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  9:05 Zhiwei Ying
2011-04-01 10:59 ` Adrien Kunysz
2011-04-01 12:27   ` Zhiwei Ying
2011-04-01 18:25 ` Josh Stone [this message]
2011-04-02  0:52   ` Zhiwei Ying
2011-04-04 22:56     ` Josh Stone
2011-04-06  6:03       ` Zhiwei Ying

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=4D961887.3000200@redhat.com \
    --to=jistone@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=zhiwei.ying@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).