From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/13296] New: inaccessible sdt.h operands of the form symbol(%reg)
Date: Fri, 14 Oct 2011 12:15:00 -0000 [thread overview]
Message-ID: <bug-13296-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13296
Bug #: 13296
Summary: inaccessible sdt.h operands of the form symbol(%reg)
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap@sourceware.org
ReportedBy: fche@redhat.com
Classification: Unclassified
We have encountered cases where the compiler emits assembler operands
for sdt.h parameters that cannot possibly be processed by stap (like
in the case of referring to local labels that are lost during the
compilation/linking stage). The cure for that has been to use
something like -DSTAP_SDT_ARG_CONSTRAINT=r to force values into
registers.
However, we should at least attempt to resolve globals in the symbol
table, within sdt_uprobe_var_expanding_visitor::visit_target_symbol_arg.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-10-14 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 12:15 fche at redhat dot com [this message]
2011-10-14 12:29 ` [Bug translator/13296] " rrakus at fedoraproject dot org
2011-10-14 12:36 ` fche at redhat dot com
2011-10-14 13:56 ` sergiodj at redhat dot com
2011-10-18 13:18 ` mjw at redhat dot com
2011-12-01 2:51 ` fche at redhat dot com
2014-02-08 8:40 ` kalvdans at gmail dot com
2014-05-05 20:24 ` jlebon at redhat dot com
2014-05-09 20:39 ` jlebon 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-13296-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).