From: "Frank Ch. Eigler" <fche@redhat.com>
To: Frans Verster <fverster@gmail.com>
Cc: systemtap@sources.redhat.com
Subject: Re: SystemTap
Date: Sat, 21 Nov 2009 14:48:00 -0000 [thread overview]
Message-ID: <20091121144713.GC29296@redhat.com> (raw)
In-Reply-To: <1cd351fc0911210529p95d3208k35d490d77225d162@mail.gmail.com>
Hi -
> OK as soon as it works nicely i will add [ubuntu kernel rebuild
> instructions] to the wiki.
Great.
> I am trying out the samples, with one i have troubles, can you run
> inodewatch-simple.stp ?
Not quite; the old scripts transcribed into the documentation fell
behind modern kernels. $file->f_dentry would need to be replaced with
$file->f_path->dentry. The tapset library of script fragments is
meant to hide such changes (see tapset/vfs.stp for example), but that
script must have been written with an older version of the tapset in
mind. With current tapset actually, you'd replace those two whole
$-expressions with:
dev_nr = dev
ino_nr = ino
since vfs.read/.write provide "cooked" dev & ino values.
See $prefix/share/doc/systemtap*/examples for more current samples.
- FChE
next parent reply other threads:[~2009-11-21 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1cd351fc0911180659k7c49c97fk7e0b6463764f3894@mail.gmail.com>
[not found] ` <20091118150807.GB12292@redhat.com>
[not found] ` <1cd351fc0911180757l128dad05s44a2d689d5489d82@mail.gmail.com>
[not found] ` <20091120152420.GD12292@redhat.com>
[not found] ` <1cd351fc0911210529p95d3208k35d490d77225d162@mail.gmail.com>
2009-11-21 14:48 ` Frank Ch. Eigler [this message]
2021-07-09 17:44 systemtap 王秋从
[not found] <4536208E.1010109@bull.net>
2006-10-20 22:34 ` Systemtap Vara Prasad
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=20091121144713.GC29296@redhat.com \
--to=fche@redhat.com \
--cc=fverster@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).