"No match for probe point" for syscall.open with tutorial example strace-open.stp

[Fredy Neeser <Fredy dot Neeser at solnet dot ch>]

Hi,

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.

For systemtap installation, I followed the README on
http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~//src/README?cvsroot=systemtap
and also observed
http://sourceware.org/systemtap/wiki/SystemTapWithSelfBuiltKernel

Installation went fine after I had applied the fix for the patched elfutils
reported at
	http://blog.gmane.org/gmane.linux.systemtap/day=20070629

The
        stap -vv hello-world.stp

example from the tutorial

        http://sourceware.org/systemtap/tutorial/

works just fine, but the next tutorial example

        [root@mythen stap_tests]# stap -vvv strace-open.stp

gives "No match for probe point" for syscall.open:

SystemTap translator/driver (version 0.6/0.128 built 2007-08-23)
Copyright (C) 2005-2007 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
Created temporary directory "/tmp/stapyFwODp"
Searched '/usr/local/share/systemtap/tapset/i686/*.stp', found 1
Searched '/usr/local/share/systemtap/tapset/*.stp', found 36
Searched '/usr/local/share/systemtap/tapset/LKET/*.stp', found 19
Pass 1: parsed user script and 56 library script(s) in 320usr/10sys/356real ms.
control symbols: kts: 0x0 kte: 0x0 stext: 0x0
parsed 'sys_open' -> func 'sys_open'
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 'compat_sys_open' -> func 'compat_sys_open'
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 'sys32_open' -> func 'sys32_open'
focused on module 'kernel = [0x100000-0x2bd504, bias 0x0] file
/boot/vmlinux-2.6.18-nfd1 ELF machine i?86 (code 3)
semantic error: no match for probe point while resolving probe point syscall.open
Pass 2: analyzed script: 1 probe(s), 6 function(s), 0 embed(s), 0 global(s) in
340usr/1990sys/64170real ms.
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
Running rm -rf /tmp/stapyFwODp


My /boot/vmlinux-2.6.18-nfd1 is apparently found.
The kernel was built with CONFIG_DEBUG_INFO, CONFIG_KPROBES, CONFIG_RELAY and
CONFIG_DEBUG_FS set to 'y'.

The same problem occurs also when I boot into the newer 2.6.22.1 vanilla kernel.
Where could the problem be?
Any idea what to check?

Many thanks,
Fredy.


PS: The example

        cat test.stp
        probe kernel.function("*@net/socket.c") { }
        probe kernel.function("*@net/socket.c").return { }
        stap -vvv test.stp

shows the same problem:

...
Searched '/usr/local/share/systemtap/tapset/i686/*.stp', found 1
Searched '/usr/local/share/systemtap/tapset/*.stp', found 36
Searched '/usr/local/share/systemtap/tapset/LKET/*.stp', found 19
Pass 1: parsed user script and 56 library script(s) in 320usr/0sys/335real ms.
control symbols: kts: 0x0 kte: 0x0 stext: 0x0
parsed '*@net/socket.c' -> func '*', file 'net/socket.c'
focused on module 'kernel = [0x100000-0x2bd504, bias 0x0] file
/boot/vmlinux-2.6.18-nfd1 ELF machine i?86 (code 3)
semantic error: no match for probe point while resolving probe point
kernel.function("*@net/socket.c")
...