This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: "No match for probe point" for syscall.open with tutorial example strace-open.stp
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Fredy Neeser <Fredy dot Neeser at solnet dot ch>
- Cc: systemtap at sources dot redhat dot com
- Date: Thu, 23 Aug 2007 18:10:33 -0400
- Subject: Re: "No match for probe point" for syscall.open with tutorial example strace-open.stp
- References: <loom.20070823T214142-222@post.gmane.org>
Fredy Neeser <Fredy.Neeser@solnet.ch> writes:
> I am trying to use systemtap (20070818 snapshot) on an IA32 Core Duo system with
> Fedora Core 5 and a kernel which I built from vanilla 2.6.18 sources.
Thank you for your high-quality problem report!
Other than dsmith's comment, there's another telltale problem:
> [...]
> focused on module 'kernel = [0x100000-0x2bd504, bias 0x0] file /boot/vmlinux-2.6.18-nfd1 ELF machine i?86 (code 3)
> control symbols: kts: 0x0 kte: 0x0 stext: 0x0
> parsed 'sys_open' -> func 'sys_open'
> focused on module 'kernel = [0x100000-0x2bd504, bias 0x0] [...]
Before that second "focused" line, you should be seeing something like:
pattern 'sys_open' matches function 'sys_open'
selected function sys_open
probe sys_open@fs/open.c:977 kernel section=.text pc=0xc0471088
Can you do a smell test of your vmlinux file:
% ls -l /boot/vmlinux*
% readelf -S /boot/vmlinux* | grep -i debug
- FChE