[Bug tapsets/11263] New: exposing foo32 syscalls

["mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

tapset/x86_64/syscalls.stp and tapset/x86_64/nd_syscalls.stp declare a couple of
syscall names that don't actually exist. syscall.pipe32, syscall.mmap32 and
maybe some others.

These seem to be added to probe 32on64 executables calling a particular syscall.
But it seems strange to expose these as different syscall probe names. If one
would like to filter on such syscall usage one could use the probing_32bit_app()
function in the script.

If we do expose them as syscall probe variants then a different naming scheme
(syscall.32on64.<name>) might be better. And some guidance when we (also) expose
a 32bit variant on a 64bit kernel. Since currently we only seem to expose some.

-- 
           Summary: exposing foo32 syscalls
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mjw at redhat dot com


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

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