From: "Frank Ch. Eigler" <fche@redhat.com>
To: zshan <zshan@cse.buaa.edu.cn>
Cc: systemtap <systemtap@sourceware.org>
Subject: Re: Re: Re: Fw: Re: problem when running the following script
Date: Mon, 18 May 2009 04:34:00 -0000 [thread overview]
Message-ID: <20090518043338.GB17190@redhat.com> (raw)
In-Reply-To: <200905180923257051704@cse.buaa.edu.cn>
Hi -
On Mon, May 18, 2009 at 09:23:26AM +0800, zshan wrote:
> > Well, maybe the TUN driver is not compiled into your kernel at all.
> > Maybe it's somehow lumped into another module. (There is likely no
> > "tun-debuginfo" package.)
> I run the script and it shows that:
> semantic error: no match while resolving probe point module("*").function("tun*")
> [root@localhost ~]# stap -l 'kernel.function("tun*")'
> semantic error: no match while resolving probe point kernel.function("tun*")
grep TUN in your kernel .config file; grep tun_ in /proc/kallsyms.
If empty, you don't have tun built, so pick another driver/module.
Check that you have the correct version debuginfo for your kernel.
Try the debuginfo-free kprobes.function("FOOBAR") variant.
- FChE
next prev parent reply other threads:[~2009-05-18 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905091541529849322@cse.buaa.edu.cn>
[not found] ` <200905101256432501377@cse.buaa.edu.cn>
2009-05-10 15:06 ` Frank Ch. Eigler
[not found] ` <200905110005329536333@cse.buaa.edu.cn>
2009-05-17 18:02 ` Frank Ch. Eigler
[not found] ` <200905180923257051704@cse.buaa.edu.cn>
2009-05-18 4:34 ` Frank Ch. Eigler [this message]
[not found] ` <200905192224248083495@cse.buaa.edu.cn>
2009-05-19 14:57 ` Frank Ch. Eigler
[not found] ` <200905192316411523143@cse.buaa.edu.cn>
2009-05-19 15:27 ` Frank Ch. Eigler
[not found] ` <200905192324558244437@cse.buaa.edu.cn>
2009-05-19 15:31 ` Frank Ch. Eigler
2009-05-19 17:07 ` Mark Wielaard
[not found] ` <200905210813228089986@cse.buaa.edu.cn>
2009-05-21 6:16 ` Mark Wielaard
2009-05-23 13:13 ` Mark Wielaard
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=20090518043338.GB17190@redhat.com \
--to=fche@redhat.com \
--cc=systemtap@sourceware.org \
--cc=zshan@cse.buaa.edu.cn \
/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).