This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: utrace syscall arguments
- From: Roland McGrath <roland at redhat dot com>
- To: David Smith <dsmith at redhat dot com>
- Cc: Systemtap List <systemtap at sources dot redhat dot com>
- Date: Fri, 17 Apr 2009 11:39:04 -0700 (PDT)
- Subject: Re: utrace syscall arguments
- References: <49E8967F.6000604@redhat.com>
> [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>)
That just looks like an strace bug for s390x biarch.
I'm a little confused as to how your stap test suite cares what strace thinks.
> [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.
I'm confused. You can only get the syscall arguments at entry time, before
it is decided whether it succeeds or fails. Or do you mean using a bogus
system call number?
Thanks,
Roland