[Bug tapsets/11163] New: on ppc, 'syscall.readv' and 'syscall.writev' aliases report an "unknown" fd

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

On ppc, the 'syscall.readv' and 'syscall.writev' aliases report the fd as
"unknown".  This is because of the following commit:

commit 43efac911763c31250e953fcd633d7f275d88270
Author: hien <hien>
Date:   Thu Mar 9 01:06:52 2006 +0000

    Temporary fix can't resolve $fd for readv and writev on RHEL4 U3 ppc64.

This "temporary" fix has been around for a long time now.

Here's the code:

/* FIXME: RHEL4 U3 ppc64 can't resolve $fd */
%( arch != "powerpc" %?
	fd = $fd
	argstr = sprintf("%d, %p, %d", $fd, $vec, $vlen)
%:
	argstr = sprintf("unknown fd, %p, %d", $vec, $vlen)
%)

While it may be true that RHEL4 U3 ppc64 can't resolve $fd, RHEL5 U3/U4 ppc64
can resolve $fd.

An easy workaround would be to add in a kernel version check so that "unknown"
fds are only reported for kernels of the RHEL4 era.

-- 
           Summary: on ppc, 'syscall.readv' and 'syscall.writev' aliases
                    report an "unknown" fd
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: dsmith at redhat dot com


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

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