public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/5150] New: buildok/nfs-all-probes.stp fails
Date: Tue, 09 Oct 2007 15:33:00 -0000	[thread overview]
Message-ID: <20071009153328.5150.wcohen@redhat.com> (raw)

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.

             reply	other threads:[~2007-10-09 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 15:33 wcohen at redhat dot com [this message]
2007-10-09 16:53 ` [Bug tapsets/5150] " mmlnx at us dot ibm dot com
2009-11-09 15:58 ` dsmith at redhat dot com
2009-11-09 16:00 ` dsmith at redhat dot com
2009-11-16 19:01 ` dsmith at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071009153328.5150.wcohen@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).