From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15136] New: stapdyn doesn't fill registers on 32-bit x86
Date: Mon, 11 Feb 2013 21:11:00 -0000 [thread overview]
Message-ID: <bug-15136-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15136
Bug #: 15136
Summary: stapdyn doesn't fill registers on 32-bit x86
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dyninst
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
On 32-bit x86, Dyninst currently doesn't make any registers available to
instrumentation snippets. Our code fills what it can (nothing) and writes
zeros for the rest. Thus, any code in the probe handlers which read registers
will get incorrect data, and probably error out if they try to read and
dereference a pointer.
Our code is dynamic about available registers, so once Dyninst expands its
support, stapdyn should just start working too. Thus, this bug is just for
tracking purposes, and to remind us to try again later.
--
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:[~2013-02-11 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 21:11 jistone at redhat dot com [this message]
2013-02-11 21:11 ` [Bug dyninst/15136] " jistone at redhat dot com
2020-04-24 16:58 ` cosmin.chenaru at gmail dot com
2020-04-24 17:09 ` fche 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-15136-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).