From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/20307] New: tapset/linux/rpc.stp error (possible because of 'private' keyword)
Date: Tue, 28 Jun 2016 14:05:00 -0000 [thread overview]
Message-ID: <bug-20307-6586@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2016-06-28 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 14:05 dsmith at redhat dot com [this message]
2016-06-28 15:56 ` [Bug translator/20307] tapset/linux/rpc.stp error dsmith at redhat dot com
2016-06-28 18:13 ` dsmith at redhat dot com
2016-06-29 18:33 ` dsmith at redhat dot com
2016-06-29 18:34 ` [Bug translator/20307] 'private' on tapset global arrays causes errors dsmith at redhat dot com
2016-06-29 20:44 ` fche at redhat dot com
2016-06-30 15:11 ` mcermak at redhat dot com
2016-06-30 16:11 ` fche at redhat dot com
2016-07-01 7:31 ` mcermak at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-20307-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).