This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
utrace syscall arguments
- From: David Smith <dsmith at redhat dot com>
- To: Systemtap List <systemtap at sources dot redhat dot com>
- Date: Fri, 17 Apr 2009 09:47:27 -0500
- Subject: utrace syscall arguments
After reorganizing the utrace system call argument handling, I decided
that I really needed to write a testsuite test for them. After doing
so, I ran the test, utrace_syscall_args.exp, on several systems.
In case anyone is interested, here's what I found:
arch distro kernel 64-bit 32-bit
====== ======= ============================== ======= =======
x86_64 f10 2.6.27.21-170.2.56.fc10.x86_64 pass pass
x86_64 rawhide 2.6.29.1-70.fc11.x86_64 pass pass
i686 RHEL5.3 2.6.18-128.1.6.el5 ---- pass
x86_64 RHEL5.3 2.6.18-128.1.6.el5 pass fail[1]
ppc64 RHEL5.3 2.6.18-138.el5 pass pass
s390x RHEL5.3 2.6.18-138.el5 pass fail[2]
ia64 RHEL5.3 2.6.18-138.el5 fail[3] ----
[1] This is a kernel problem. The 6th syscall argument on 32-bit exes
on a 64-bit kernel is wrong. RHBZ 495125 filed against this problem
(<https://bugzilla.redhat.com/show_bug.cgi?id=495125>)
[2] This might just be an system call that needs some extra processing
or a kernel problem. RHBZ 495935 filed against this problem
(<https://bugzilla.redhat.com/show_bug.cgi?id=495935>)
[3] This appears to be an ia64 specific systemtap problem that someone
with actual ia64 knowledge will need to look at. For system calls that
fail, all arguments come back as zeros.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)