From: "bharata at linux dot vnet dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/4904] Wrong ordering of probepoints in stap output + incorrect lising probepoints by kprobes
Date: Wed, 08 Aug 2007 11:11:00 -0000 [thread overview]
Message-ID: <20070808083506.19683.qmail@sourceware.org> (raw)
In-Reply-To: <20070808060340.4904.bharata@linux.vnet.ibm.com>
------- Additional Comments From bharata at linux dot vnet dot ibm dot com 2007-08-08 08:35 -------
Ok, I replaced all kernel.function probes with kernel.statement probes, but
ended up in other problems. I now get errors like this:
semantic error: multiple addresses for fs/namespace.c:1826 (try
fs/namespace.c:1825 or fs/namespace.c:1827)
semantic error: no match for probe point while resolving probe point
kernel.statement("*@fs/namespace.c:1826")
semantic error: multiple addresses for fs/namespace.c:1834 (try
fs/namespace.c:1833 or fs/namespace.c:1836)
semantic error: no match for probe point while resolving probe point
kernel.statement("*@fs/namespace.c:1834")
semantic error: multiple addresses for fs/namespace.c:1858 (try
fs/namespace.c:1857 or fs/namespace.c:1859)
semantic error: no match for probe point while resolving probe point
kernel.statement("*@fs/namespace.c:1858")
semantic error: multiple addresses for fs/namespace.c:1868 (try
fs/namespace.c:1867 or fs/namespace.c:1869)
semantic error: no match for probe point while resolving probe point
kernel.statement("*@fs/namespace.c:1868")
If you look at the first error here stap is asking me to either
- put probe on 1825 which is a blank line which is blank line. This won't work
(see bug #4899)
or
- put probe on 1827 which is not a valid full C statement.
Am I just unfamiliar with stap usage or is this a bug ?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4904
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-08-08 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 6:21 [Bug runtime/4904] New: " bharata at linux dot vnet dot ibm dot com
2007-08-08 7:00 ` [Bug runtime/4904] " bharata at linux dot vnet dot ibm dot com
2007-08-08 8:35 ` joshua dot i dot stone at intel dot com
2007-08-08 11:11 ` srinivasa at in dot ibm dot com
2007-08-08 11:11 ` bharata at linux dot vnet dot ibm dot com [this message]
2007-08-08 16:25 ` fche at redhat dot com
2007-08-08 16:30 ` [Bug runtime/4904] hard to use statement probes for line-by-line tracing fche at redhat dot com
2008-01-21 14:28 ` srinivasa at in dot ibm dot com
2008-01-21 14:43 ` fche at redhat dot com
2008-01-21 14:46 ` fche at redhat dot com
2008-01-22 10:12 ` srinivasa at in dot ibm dot com
2008-06-12 13:23 ` scox 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=20070808083506.19683.qmail@sourceware.org \
--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).