This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug uprobes/10458] uaddr() returns one past current instruction for uprobes


------- 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]