This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/5510] New: no match while resolving probe point sunrpc.sched.release_task.return
- From: "baiwd at cn dot fujitsu dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 19 Dec 2007 01:15:02 -0000
- Subject: [Bug tapsets/5510] New: no match while resolving probe point sunrpc.sched.release_task.return
- Reply-to: sourceware-bugzilla at sourceware dot org
On RHEL5.1, I test systemtap(20071215 version) with
buildok/rpc-all-probes.stp, it reports that:
Pass 1: parsed user script and 38 library script(s) in 306usr/5sys/310real ms.
semantic error: no match while resolving probe point
sunrpc.sched.release_task.return
I think that this is caused by that sunrpc.sched.release_task.return is not
necessarily exist. As you can see:
probe sunrpc.sched.release_task.return =
kernel.function("rpc_release_task").return ?,
module("sunrpc").function("rpc_release_task").return ?
{
name = "sunrpc.sched.release_task.return"
}
So I want to change it as follwowing:
--- /home/baiwd/stapsrc/src/tapset/rpc.stp 2007-11-08 11:02:47.000000000 +0900
+++ ./rpc.stp 2007-12-18 18:39:44.000000000 +0900
@@ -724,7 +724,7 @@ probe sunrpc.sched.entry =
probe sunrpc.sched.return =
sunrpc.sched.new_task.return,
- sunrpc.sched.release_task.return,
+ sunrpc.sched.release_task.return ?,
sunrpc.sched.execute.return,
sunrpc.sched.delay.return
{}
Is this fix right?
--
Summary: no match while resolving probe point
sunrpc.sched.release_task.return
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: baiwd at cn dot fujitsu dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5510
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.