This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/20307] New: tapset/linux/rpc.stp error (possible because of 'private' keyword)
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 28 Jun 2016 14:05:43 +0000
- Subject: [Bug translator/20307] New: tapset/linux/rpc.stp error (possible because of 'private' keyword)
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20307
Bug ID: 20307
Summary: tapset/linux/rpc.stp error (possible because of
'private' keyword)
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
I'm seeing something odd with rpc.stp:
====
# stap -vp4 ../src/testsuite/buildok/rpc-all-probes.stp
Pass 1: parsed user script and 115 library scripts using
159296virt/42368res/8576shr/29248data kb, in 490usr/0sys/489real ms.
WARNING: cannot probe .return of 1 inlined functions rpc_release_task
WARNING: cannot probe .return of 1 inlined functions rpc_release_task
WARNING: cannot probe .return of 1 inlined functions rpc_release_task
WARNING: cannot probe .return of 1 inlined functions rpc_release_task
WARNING: cannot probe .return of 1 inlined functions rpc_release_task
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at
/usr/local/share/systemtap/tapset/linux/rpc.stp:182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
semantic error: unresolved arity-1 global array __rpc_create_args, missing
global declaration?: identifier '__rpc_create_args' at :182:12
source: __args = __rpc_create_args[tid()]
^
Pass 2: analyzed script: 158 probes, 880 functions, 9 embeds, 1 global using
274048virt/159104res/10624shr/144000data kb, in 24400usr/490sys/24885real ms.
Pass 2: analysis failed. [man error::pass2]
====
Off the top of my head, I'd guess that the 'private' keyword applied to that
global array is somehow causing this problem. '__rpc_create_args' is declared
in that file like:
====
@__private30 global __rpc_create_args
====
--
You are receiving this mail because:
You are the assignee for the bug.