[Bug tapsets/2295] support conditionally present syscalls

joshua dot i dot stone at intel dot com sourceware-bugzilla@sourceware.org
Fri Jun 2 19:25:00 GMT 2006


------- Additional Comments From joshua dot i dot stone at intel dot com  2006-06-02 19:25 -------
On x86_64 FC5, buildok/syscall.stp gives me this:

semantic error: no match for probe point
while: resolving probe point kernel.function("sys_ftruncate64")
semantic error: no match for probe point
while: resolving probe point kernel.function("sys_truncate64")
semantic error: no match for probe point
while: resolving probe point kernel.function("sys_ftruncate64").return
semantic error: no match for probe point
while: resolving probe point kernel.function("sys_truncate64").return
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.


With the resolution of bug #2645, missing or conditionally-present syscalls can
probably be marked with "?", so that syscall.* can still work in their absence.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2295

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the Systemtap mailing list