[Bug tapsets/5772] New: systemtap.syscall/sys.stp fails on systemtap-20080216

[srinivasa at in dot ibm dot com]

There is a difference in argument name of sys_waitid and sys_wait4 systemcall.
This is not reflected in current tapsets. Hence sys.stp fails.
=============================
emantic error: not accessible at this address: identifier '$pid' at
/home/systemtap/tmp/stap_testing_200802190556/install/share/systemtap/tapset/syscalls2.stp:3031:37
semantic error: not accessible at this address: identifier '$pid' at
/home/systemtap/tmp/stap_testing_200802190556/install/share/systemtap/tapset/syscalls2.stp:3055:49
====================================

2.6.24-rc8
==========
asmlinkage long sys_waitid(int which, pid_t pid,
                           struct siginfo __user *infop, int options,
                           struct rusage __user *ru)
{
============
2.6.25-rc2
=============
asmlinkage long sys_waitid(int which, pid_t upid,
                           struct siginfo __user *infop, int options,
                           struct rusage __user *ru)
{
==============

-- 
           Summary: systemtap.syscall/sys.stp fails on systemtap-20080216
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: srinivasa at in dot ibm dot com


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

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