This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Re: Re: Fw: Re: problem when running the following script
- From: "Frank Ch. Eigler" <fche at redhat dot com>
- To: zshan <zshan at cse dot buaa dot edu dot cn>
- Cc: systemtap <systemtap at sourceware dot org>
- Date: Mon, 18 May 2009 00:33:38 -0400
- Subject: Re: Re: Re: Fw: Re: problem when running the following script
- References: <20090517180158.GA17190@redhat.com> <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