This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails
- From: "wcohen at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 9 Oct 2007 15:33:28 -0000
- Subject: [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails
- Reply-to: sourceware-bugzilla at sourceware dot org
With the 2.6.23-rc9 kernel the probe points for some of the nfs.* nfs.*.* probes
are available.
Running /home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp
starting
/home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp
spawn1 stap -p4
/home/wcohen/stap_snap_200710081315/src/testsuite/buildok/nfs-all-probes.stp
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile.return
semantic error: no match for probe point while resolving probe point
nfs.fop.sendfile.return
semantic error: no match for probe point while resolving probe point
nfs.proc3.commit
semantic error: no match for probe point while resolving probe point
nfs.proc3.commit
semantic error: no match for probe point while resolving probe point
nfs.proc4.commit
semantic error: no match for probe point while resolving probe point
nfs.proc4.commit
semantic error: no match for probe point while resolving probe point nfs.proc2.read
semantic error: no match for probe point while resolving probe point nfs.proc2.read
semantic error: no match for probe point while resolving probe point nfs.proc3.read
semantic error: no match for probe point while resolving probe point nfs.proc3.read
semantic error: no match for probe point while resolving probe point nfs.proc4.read
semantic error: no match for probe point while resolving probe point nfs.proc4.read
semantic error: no match for probe point while resolving probe point nfs.proc.read
semantic error: no match for probe point while resolving probe point nfs.proc.read
semantic error: no match for probe point while resolving probe point nfs.proc2.write
semantic error: no match for probe point while resolving probe point nfs.proc2.write
semantic error: no match for probe point while resolving probe point nfs.proc3.write
semantic error: no match for probe point while resolving probe point nfs.proc3.write
semantic error: no match for probe point while resolving probe point nfs.proc4.write
semantic error: no match for probe point while resolving probe point nfs.proc4.write
semantic error: no match for probe point while resolving probe point nfs.proc.write
semantic error: no match for probe point while resolving probe point nfs.proc.write
semantic error: no match for probe point while resolving probe point nfs.proc.commit
semantic error: no match for probe point while resolving probe point nfs.proc.commit
semantic error: no match for probe point while resolving probe point
nfs.proc2.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc2.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc3.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc3.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc4.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc4.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc.read.return
semantic error: no match for probe point while resolving probe point
nfs.proc2.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc2.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc3.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc3.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc4.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc4.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc.write.return
semantic error: no match for probe point while resolving probe point
nfs.proc3.commit.return
semantic error: no match for probe point while resolving probe point
nfs.proc3.commit.return
semantic error: no match for probe point while resolving probe point
nfs.proc4.commit.return
semantic error: no match for probe point while resolving probe point
nfs.proc4.commit.return
semantic error: no match for probe point while resolving probe point
nfs.proc.commit.return
semantic error: no match for probe point while resolving probe point
nfs.proc.commit.return
Pass 2: analysis failed. Try again with more '-v' (verbose) options.
Pass 2: analysis failed. Try again with more '-v' (verbose) options.
wait results: 2766 exp15 0 1
FAIL: buildok/nfs-all-probes.stp
--
Summary: buildok/nfs-all-probes.stp fails
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
http://sourceware.org/bugzilla/show_bug.cgi?id=5150
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.