public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: corpaul <c.bezemer@tudelft.nl>
Cc: systemtap@sourceware.org
Subject: Re: user-space tracing on Debian... or..?
Date: Fri, 15 Mar 2013 15:13:00 -0000	[thread overview]
Message-ID: <y0m1ubgg0hg.fsf@fche.csb> (raw)
In-Reply-To: <1363355658749-225525.post@n7.nabble.com> (c.bezemer@tudelft.nl's message of "Fri, 15 Mar 2013 06:54:18 -0700 (PDT)")


c.bezemer wrote:

> [...]  So is there another way to set probes on all function
> returns, rather than creating a new probe explicitly for every
> return using the line number?  [...]

With a basic facility missing in the kernel, systemtap users are
forced to wait for "uretprobes" to be finished / merged.

An alternative is the stap --runtime=dyninst backend, which would have
to be enabled in your systemtap build/distro, and is still relatively
young code.

(Another alternative is to use an older Fedora or any RHEL[56] distro,
where the kernel utrace patches were applied, and thus systemtap users
have full function-return-probing powers.)

- FChE

  reply	other threads:[~2013-03-15 15:13 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
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 [this message]
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=y0m1ubgg0hg.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=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).