public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/24327] @defined unable to handle $$parms and $$vars meta variables
Date: Wed, 13 Mar 2019 18:26:00 -0000	[thread overview]
Message-ID: <bug-24327-6586-GtYPLfVu6d@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24327-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24327

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
This code is related to the automatic printing of global variables.  It can be
turned off and allows the reproducer to compile and run:

[wcohen@cervelo systemtap]$ stap  -e 'probe
kernel.statement("do_sys_open@fs/open.c:*") {if (@defined($$parms)) printf("%s
\n", $$parms); exit()}'
parse error: expected identifier or statistical operation
        saw: operator '-' at <input>:2:30
     source: foreach (__val = [__idx0] in -)
                                          ^
        in synthesized code from: identifier '$$parms' at <input>:1:65
     source: probe kernel.statement("do_sys_open@fs/open.c:*") {if
(@defined($$parms)) printf("%s \n", $$parms); exit()}
                                                                             ^

Segmentation fault (core dumped)
[wcohen@cervelo systemtap]$ stap  --no-global-var-display -e 'probe
kernel.statement("do_sys_open@fs/open.c:*") {if (@defined($$parms)) printf("%s
\n", $$parms); exit()}'
dfd=0xffffffffffffff9c filename=0x7fe33bffe6e0 flags=0x8000 mode=0x0

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2019-03-13 18:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 20:16 [Bug translator/24327] New: " wcohen at redhat dot com
2019-03-13 18:16 ` [Bug translator/24327] " wcohen at redhat dot com
2019-03-13 18:26 ` wcohen at redhat dot com [this message]
2019-03-13 21:06 ` wcohen 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-24327-6586-GtYPLfVu6d@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).