This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/9876] Syscall tapset broken on architectures that use SYSCALL_WRAPPERS
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 21 Feb 2009 15:27:03 -0000
- Subject: [Bug tapsets/9876] Syscall tapset broken on architectures that use SYSCALL_WRAPPERS
- References: <20090220112441.9876.ananth@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2009-02-21 15:27 -------
There are some hunks that don't use "!" but rather "?" (syscall.writev.return,
syscall.mount, ...), probably because there are "compat" variants also. This
can still result in double-counting syscalls, so please write & run a test case
to check for this.
If a problem exists, this might solve it. Instead of this ...
probe syscall.mount =
kernel.function("SyS_mount") ?,
kernel.function("sys_mount") ?,
kernel.function("compat_sys_mount") ?
try
probe syscall.mount =
kernel.function("compat_sys_mount") ?
kernel.function("SyS_mount") !,
kernel.function("sys_mount")
It all depends whether any of these sibling functions can call each other.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=9876
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.