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 21:06:00 -0000 [thread overview]
Message-ID: <bug-24327-6586-OnVSOAG8g1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24327-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24327
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
The following patch checked into upstream systemtap fixes the problem.
commit 76517421a569be2d7cd90302f15b63d5cfb0bc75 (HEAD -> master, origin/master,
origin/HEAD)
Author: Jafeer Uddin <juddin@redhat.com>
Date: Wed Mar 13 16:12:45 2019 -0400
PR24327: Remove printing of unused synthetic globals
The handling of DW_OP_GNU_entry_value introduces synthetic
global variables that after optimizations may end up not
being used. The default behaviour is to print out the values
of unsued globals in user scripts. This printing is intended
for user defined globals and shouldn't occur with the generated
globals.
The reproducer works fine now:
$ ../install/bin/stap -e 'probe kernel.statement("do_sys_open@fs/open.c:*")
{if (@defined($$parms)) printf("%s \n", $$parms); exit()}'
dfd=0xffffffffffffff9c filename=0x7ffd2e4c4590 flags=0x98800 mode=0x0
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-03-13 21:06 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
2019-03-13 21:06 ` wcohen at redhat dot com [this message]
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-OnVSOAG8g1@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).