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

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2007-08-08 11:10 -------
> Ok, I replaced all kernel.function probes with kernel.statement probes, but
> ended up in other problems. I now get errors like this [...]

You are seeing effects of the smearing of statements due to compiler optimization.
Often, there isn't a single appropriate address to probe for a given statement
position.

We should do better in handling such cases though:
* suggested alternatives should be confirmed usable so that a user is not led astray
* consider applying more aggressive heuristics to map a user's request into a
probe "nearby", even if not strictly correct in some sense
* a probe syntax should be available to allow systemtap to search for all
probe-able lines in a range: perhaps something like
   foo.statement("*@file.c:200-300")


-- 


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.