From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/15688] New: Accessing globals in DSO or PIE results in read faults
Date: Thu, 27 Jun 2013 02:02:00 -0000 [thread overview]
Message-ID: <bug-15688-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15688
Bug ID: 15688
Summary: Accessing globals in DSO or PIE results in read faults
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
I've noticed that use of @var("foo") or $foo in either probe process.function
or probe process.mark could lead to the following error when there is a global
variable named "foo" in the current userspace DSO or PIE module:
ERROR: read fault [man error::fault] at 0x (null) (addr) near
operator '@var'
It seems that dwarf_var_expanding_visitor::visit_target_symbol can resolve the
variable into a global variable but does not enable the VMA tracker for the
current module accordingly.
I can always reproduce this with trivial example on the current master (commit
5883b785fa)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-06-27 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 2:02 agentzh at gmail dot com [this message]
2013-06-27 16:05 ` [Bug translator/15688] " jistone at redhat dot com
2013-06-27 19:37 ` agentzh at gmail dot com
2013-06-27 22:17 ` jistone at redhat dot com
2013-06-27 22:51 ` jistone 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-15688-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).