Bug 11162 - on s390x, the 'syscall.pwrite32' tapset alias fails to compile
Summary: on s390x, the 'syscall.pwrite32' tapset alias fails to compile
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: tapsets (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-12 19:54 UTC by David Smith
Modified: 2010-01-12 19:59 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Smith 2010-01-12 19:54:15 UTC
on s390x (kernel 2.6.18-164.el5), the following error occurs:

====
# stap -ve 'probe syscall.pwrite32 { printf("%d\n", buf_uaddr) }'
Pass 1: parsed user script and 65 library script(s) using
28656virt/20192res/2560shr kb, in 360usr/10sys/380real ms.
semantic error: unable to find local 'buf' near pc 0x113dfc in
sys32_pwrite64(arch/s390/kernel/compat_linux.c) (alternatives: fd ubuf count
poshi poslo): identifier '$buf' at
/usr/local/share/systemtap/tapset/syscalls2.stp:575:14
        source: 	buf_uaddr = $buf
                	            ^
Pass 2: analyzed script: 1 probe(s), 1 function(s), 0 embed(s), 0 global(s)
using 72464virt/53480res/26440shr kb, in 320usr/200sys/525real ms.
Pass 2: analysis failed.  Try again with another '--vp 01' option.
====

On s390x, '$buf' should be '$ubuf'.
Comment 1 David Smith 2010-01-12 19:59:15 UTC
Fixed in commit ed8c793.