From: corpaul <c.bezemer@tudelft.nl>
To: systemtap@sourceware.org
Subject: Re: user-space tracing on Debian... or..?
Date: Wed, 13 Mar 2013 07:33:00 -0000 [thread overview]
Message-ID: <1363160027043-225252.post@n7.nabble.com> (raw)
In-Reply-To: <84obeo8jbs.fsf@sauna.l.org>
I tried with a custom 3.8.x. kernel.
Also I tried with the latest Fedora which uses a 3.6.x kernel.
Both use Systemtap 2.1.
For both kernels I get an error when I try to run the probe:
probe process("./test").function("main").return
{
printf("Main function exited\n");
}
Error:
Pass 1: parsed user script and 97 library script(s) using
216852virt/35972res/2972shr/33668data kb, in 230usr/50sys/507real ms.
semantic error: while resolving probe point: identifier 'process' at
test.stp:2:7
source: probe process("./test").function("main").return
^
semantic error: process return probes not available [man
error::inode-uprobes]
Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s)
using 217908virt/37272res/3116shr/34724data kb, in 10usr/10sys/27real ms.
Pass 2: analysis failed. [man error::pass2]
From what I understand is that it has something to do with the fact that
Systemtap uses Uprobes instead of Utrace in newer kernels. Is there any way
I can run probes of this type? Or is there a workaround to be able to run a
probe with the same effect?
Thanks! CP
--
View this message in context: http://sourceware-org.1504.n7.nabble.com/user-space-tracing-on-Debian-or-tp225167p225252.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.
next prev parent reply other threads:[~2013-03-13 7:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:34 corpaul
2013-03-12 16:52 ` Frank Ch. Eigler
2013-03-12 20:16 ` Timo Juhani Lindfors
2013-03-13 7:33 ` corpaul [this message]
2013-03-13 14:28 ` Lukas Berk
2013-03-13 14:32 ` Timo Juhani Lindfors
2013-03-15 13:54 ` corpaul
2013-03-15 15:13 ` Frank Ch. Eigler
2013-03-28 10:26 ` corpaul
2013-03-28 14:26 ` Frank Ch. Eigler
2013-03-28 16:25 ` Josh Stone
2013-03-28 16:45 ` Josh Stone
2013-04-05 13:38 ` corpaul
2013-04-05 13:58 ` Timo Juhani Lindfors
2013-04-05 14:02 ` Cor-paul Bezemer - EWI
2013-04-05 14:06 ` Timo Juhani Lindfors
2013-04-05 14:07 ` Cor-paul Bezemer - EWI
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=1363160027043-225252.post@n7.nabble.com \
--to=c.bezemer@tudelft.nl \
--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).