[Bug testsuite/10007] New: Some SystemTap tests need updates to handle SYSCALL_WRAPPERS

["ananth at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

On some architectures, the Linux kernel uses syscall wrappers due to which the
old style sys_read type functions now need to be referred by SyS_read. Many
tests in the SystemTap refer to the old style system calls directly, and don't
use the syscall tapset, that can alleviate the problem.

We should either:
a. Fix the tests to refer to the different routines in different architectures
b. Better still, just make them use the syscall tapset aliases
c. Use a different non-conflicting named routines altogether.

eg:
On s390, we see a lot of testsuite failures triggered by errors similar to:
semantic error: no match while resolving probe point
kernel.function("sys_read").return
semantic error: no match while resolving probe point
kernel.function("sys_read").return
semantic error: no match while resolving probe point
kernel.function("sys_open").return
semantic error: no match while resolving probe point
kernel.function("sys_open").return

-- 
           Summary: Some SystemTap tests need updates to handle
                    SYSCALL_WRAPPERS
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: ananth at in dot ibm dot com


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

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