This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/4551] New: RHEL4U5 kernel missing a number of function used by buildok/syscall.stp
- From: "wcohen at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 25 May 2007 21:13:57 -0000
- Subject: [Bug tapsets/4551] New: RHEL4U5 kernel missing a number of function used by buildok/syscall.stp
- Reply-to: sourceware-bugzilla at sourceware dot org
A number of the syscall points fail for buildok/syscall.stp testsuite on i686
RHEL4U5 kernel, 2.6.9-55.ELsmp.
spawn1 stap -p4
/home/wcohen/stap_testing_200705251949/src/testsuite/buildok/syscall.stp
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_add_watch")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_add_watch")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_init")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_init")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_rm_watch")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_rm_watch")
semantic error: no match for probe point while resolving probe point
kernel.function("do_sched_setscheduler")
semantic error: no match for probe point while resolving probe point
kernel.function("do_sched_setscheduler")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_set_zone_reclaim")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_set_zone_reclaim")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_shmat")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_shmat")
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_add_watch").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_add_watch").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_init").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_init").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_rm_watch").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_inotify_rm_watch").return
semantic error: no match for probe point while resolving probe point
kernel.function("do_sched_setscheduler").return
semantic error: no match for probe point while resolving probe point
kernel.function("do_sched_setscheduler").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_set_zone_reclaim").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_set_zone_reclaim").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_shmat").return
semantic error: no match for probe point while resolving probe point
kernel.function("sys_shmat").return
These probe points are defined in src/tapset/i686/syscalls.stp.
--
Summary: RHEL4U5 kernel missing a number of function used by
buildok/syscall.stp
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: wcohen at redhat dot com
GCC host triplet: i686
http://sourceware.org/bugzilla/show_bug.cgi?id=4551
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.