From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/14573] New: Pass pt_regs to dyninst probe handlers
Date: Wed, 12 Sep 2012 21:21:00 -0000 [thread overview]
Message-ID: <bug-14573-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14573
Bug #: 14573
Summary: Pass pt_regs to dyninst probe handlers
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dyninst
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
In order to examine much process state with stapdyn, we're going to need
registers. We should pass a pt_regs* (/usr/include/asm/ptrace.h) as a
parameter to the probe handler.
I believe this can be allocated and prepared via BPatch_register code snippets.
We will probably need to hardcode architecture-specific support for the
register layouts, but I think that's ok as these are generally unchanging.
Not all registers will be available. Right now dyninst only exposes the
general purpose registers, and none of the special registers. We do need
access to the frame and stack pointers, but that should come soon - see:
https://lists.cs.wisc.edu/archive/dyninst-api/2012/msg00093.shtml
--
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:[~2012-09-12 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 21:21 jistone at redhat dot com [this message]
2012-10-11 17:20 ` [Bug dyninst/14573] " jistone at redhat dot com
2013-02-11 21:11 ` jistone at redhat dot com
2013-06-12 2:24 ` jistone at redhat dot com
2013-06-12 21:10 ` jistone at redhat dot com
2020-06-05 13:47 ` scox at redhat dot com
2020-06-16 20:34 ` scox 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-14573-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).