[Bug tapsets/4475] New: ia64 syscall tapset issues.

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

On ia64 some of the testsuite/systemtap.syscall/syscall.exp tests are not
working on ia64 rhel4u5. The tests that appeared to failed because some function
parameter was reported as "<unknown>" or "UNKNOWN". It appears that some of the
arguments passed into the function were missing. This seems to be a problem
mostly for "open()". An example on acct test output was:

acct: acct (<unknown>) = -1 (EPERM)

was expecting to match:

acct: acct \("foobar"\) = -[\-0-9]+

For a couple of the tests, alarm and rt_signal some functions are not being
called. For forkwait it "fork_kernel_thread()" is used rather than "clone()"

A summary of the ia64 test results problems:


FAIL: 64-bit acct	unknown arg on acct
FAIL: 64-bit alarm	unknown arg on nanosleep , no alarm or pause calls
FAIL: 64-bit chmod	unknown arg on open
FAIL: 64-bit dir	unknown arg on open
FAIL: 64-bit forkwait (actually because of fork_kernel_thread() used
		instead of "clone")
FAIL: 64-bit link	unknown arg on link
FAIL: 64-bit mmap	unknown arg on open
FAIL: 64-bit mount	unknown arg on mount
FAIL: 64-bit net1	missing arg for fcntl cmd_str
FAIL: 64-bit openclose	unknown arg on open, bogus arg on close
FAIL: 64-bit readwrite	unknown arg on open
FAIL: 64-bit rt_signal	no rt_sigprocmask calls
UNSUPPORTED: signal not supported on this arch
FAIL: 64-bit stat	unknown arg on open
FAIL: 64-bit statfs	pointers values don't match

-- 
           Summary: ia64 syscall tapset issues.
           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: ia64


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

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