[Bug tapsets/4553] New: i686 RHEL4u5 systemcall tapset argument issues with 2.6.9-55.ELsmp kernel

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

A number of the systemtap runtime tests fail on the 2.6.9-55.ELsmp kernel
because the the arguments for the systemcalls are not be generated correctly for
the kernel.

FAIL: 32-bit access
FAIL: 32-bit alarm
FAIL: 32-bit chmod
FAIL: 32-bit clock
FAIL: 32-bit dir
FAIL: 32-bit link
FAIL: 32-bit mmap
FAIL: 32-bit mount
FAIL: 32-bit net1
FAIL: 32-bit openclose
FAIL: 32-bit readwrite
FAIL: 32-bit rt_signal
FAIL: 32-bit signal
FAIL: 32-bit stat
FAIL: 32-bit statfs
FAIL: 32-bit swap
FAIL: 32-bit sync
FAIL: 32-bit timer
FAIL: 32-bit trunc
FAIL: 32-bit uid
FAIL: 32-bit uid16
FAIL: 32-bit unlink


Looking through the systemtap.log shows that many of the arguments are listed as
"<unknown>". For example output of 32-bit link includes the following output:

link: open (<unknown>,
O_RDONLY|O_APPEND|O_DIRECTORY|O_EXCL|O_LARGEFILE|O_NONBLOCK) = 4
link: close (4) = 0
link: link (<unknown>, <unknown>) = 0
link: link (<unknown>, <unknown>) = -17 (EEXIST)
link: link (<unknown>, <unknown>) = -2 (ENOENT)
link: symlink (<unknown>, <unknown>) = 0
link: readlink (<unknown>, 0x3a080300, 128) = 6
link: exit_group (0) =

-- 
           Summary: i686 RHEL4u5 systemcall tapset argument issues with
                    2.6.9-55.ELsmp kernel
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: wcohen at redhat dot com
  GCC host triplet: i686


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

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