From: "cosmin.chenaru at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15136] stapdyn doesn't fill registers on 32-bit x86
Date: Fri, 24 Apr 2020 16:58:37 +0000 [thread overview]
Message-ID: <bug-15136-6586-eLrl8c9Wyc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15136-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15136
Cosmin Chenaru <cosmin.chenaru at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cosmin.chenaru at gmail dot com
--- Comment #1 from Cosmin Chenaru <cosmin.chenaru at gmail dot com> ---
Hi. I realize I am 7 years late, but only now I had to instrument a 32-bit
application using SystemTap and Dyninst. I took a look in the latest code for
Dyninst, inside EmitterIA32::emitCall(), and to my little understanding I see
that there is still no support in passing the registers of the probe in order
for SystemTap to get them through enter_dyninst_uprobe_regs().
So can you please tell me, why can't Dyninst obtain the registers during
runtime on x86, and on x64 there is no such limitation?
Thank you.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-04-24 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 21:11 [Bug dyninst/15136] New: " jistone at redhat dot com
2013-02-11 21:11 ` [Bug dyninst/15136] " jistone at redhat dot com
2020-04-24 16:58 ` cosmin.chenaru at gmail dot com [this message]
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-eLrl8c9Wyc@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).