From: Wenji Huang <wenji.huang@oracle.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Can't access argument of process marker
Date: Fri, 25 Jun 2010 15:33:00 -0000 [thread overview]
Message-ID: <4C2446F3.1020401@oracle.com> (raw)
Hi,
I got the failure when running test semok/thirtysix.stp. The error
is triggered by the following script,
$ stap -e 'probe process("stap").mark("*")? {
println(@defined($arg1)?$arg1:$nosuchvar) }'
semantic error: invalid argument number: identifier '$nosuchvar' at
<input>:1:66
source: probe process("stap").mark("*")? {
println(@defined($arg1)?$arg1:$nosuchvar) }
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
It seems arguments of marker aren't accessible. Moreover, I think
it's not very accurate to complain "invalid argument number". In fact,
the variable doesn't follow the naming rule, it's better to make
a little modification and give some hints like $argN.
Regards,
Wenji
next reply other threads:[~2010-06-25 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 15:33 Wenji Huang [this message]
2010-06-25 17:23 ` Josh Stone
2010-06-25 18:24 ` Frank Ch. Eigler
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=4C2446F3.1020401@oracle.com \
--to=wenji.huang@oracle.com \
--cc=systemtap@sources.redhat.com \
/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).