This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/11263] exposing foo32 syscalls
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 9 Feb 2010 15:43:15 -0000
- Subject: [Bug tapsets/11263] exposing foo32 syscalls
- References: <20100209125924.11263.mjw@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mjw at redhat dot com 2010-02-09 15:43 -------
The "problem" to me is that we don't do this splitting of 32on64 versus "pure
64" bit syscalls consistently. Why do we have syscall.pipe32 and syscall.mmap32,
but not syscall.fstat32 for example?
syscall.fstat is a nice example since we make it match any syscall variant that
is called "fstat" whether it is the "plain" one or the compat/32on64 version.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11263
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.