This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/10458] uaddr() returns one past current instruction for uprobes
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 29 Jul 2009 22:32:16 -0000
- Subject: [Bug uprobes/10458] uaddr() returns one past current instruction for uprobes
- References: <20090729111010.10458.mjw@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mjw at redhat dot com 2009-07-29 22:32 -------
(In reply to comment #4)
> Forgot to mention... the probe address is always available as uprobe->vaddr or
> uretprobe->u.vaddr.
OK, that is helpful.
I am trying to figure out how to tell (in the uaddr() embedded c tapset
function) whether or not the current CONTEXT comes from a uprobe so we can use
this to provide the correct PC at that point.
Anybody know how to easily see what probe type we are in from the struct context?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10458
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.