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

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

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
{
        printf("USER, %s %s %s\n", thread_indent(1), pp(), $$parms)
}
probe process("/ddtv/tracedrv/test/dhg/hello/hello").function("*").return
{
        printf("USER %s %s %s\n", thread_indent(-1), probefunc(), $$return)
}
probe end
{
        printf ("end of tracing\n")
}

It only able to print "end of tracing", nothing in the hello is
printed. Attached is the binary of traceauto.ko.

BTW, it can trace kernel level code. Just not lucky on user-level code.

Any help is great appreciated.

Thanks,
Zhiwei

[-- Attachment #2: traceauto.ko --]
[-- Type: application/octet-stream, Size: 302835 bytes --]

             reply	other threads:[~2011-04-01  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  9:05 Zhiwei Ying [this message]
2011-04-01 10:59 ` Adrien Kunysz
2011-04-01 12:27   ` Zhiwei Ying
2011-04-01 18:25 ` Josh Stone
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=AANLkTin4+Q1r4j1LBKhv-x5-wXYf5CvryNTbOt3x71N1@mail.gmail.com \
    --to=zhiwei.ying@gmail.com \
    --cc=systemtap@sources.redhat.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).