This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/11771] New: on ppc, the syscall.pipe tapset alias fails when accessing pipe0/pipe1
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 30 Jun 2010 16:25:58 -0000
- Subject: [Bug tapsets/11771] New: on ppc, the syscall.pipe tapset alias fails when accessing pipe0/pipe1
- Reply-to: sourceware-bugzilla at sourceware dot org
kernel: 2.6.32.12-115.fc12.ppc64
# stap -vp4 -e 'probe syscall.pipe { printf("%d %d\n", pipe0, pipe1) }'
Pass 1: parsed user script and 68 library script(s) using
23724virt/13352res/2468shr kb, in 620usr/30sys/646real ms.
semantic error: invalid access '[0]' vs. long int: operator '[' at
/usr/share/systemtap/tapset/syscalls2.stp:312:29
source: pipe0 = user_int(&$fildes[0]);
^
semantic error: invalid access '[1]' vs. long int: operator '[' at :313:29
source: pipe1 = user_int(&$fildes[1]);
^
Pass 2: analyzed script: 1 probe(s), 2 function(s), 20 embed(s), 0 global(s)
using 153192virt/102280res/74456shr kb, in 1390usr/350sys/1749real ms.
Pass 2: analysis failed. Try again with another '--vp 01' option.
According to some email on the systemtap list, SYSCALL_WRAPPERS are the problem
here. SyS_foo has all "long" arguments, and then the inline SYSC_foo has the
real argument types.
This will need to be worked around in either the translator or the tapset.
--
Summary: on ppc, the syscall.pipe tapset alias fails when
accessing pipe0/pipe1
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
GCC host triplet: ppc
http://sourceware.org/bugzilla/show_bug.cgi?id=11771
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.