[Bug runtime/4904] Wrong ordering of probepoints in stap output + incorrect lising probepoints by kprobes

["bharata at linux dot vnet dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

------- 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.