* [Bug runtime/18714] New: bring back process.statement.absolute probes
@ 2015-07-24 14:51 fche at redhat dot com
2018-11-10 18:05 ` [Bug runtime/18714] " agentzh at gmail dot com
0 siblings, 1 reply; 2+ messages in thread
From: fche at redhat dot com @ 2015-07-24 14:51 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=18714
Bug ID: 18714
Summary: bring back process.statement.absolute probes
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
While inode-uprobes makes $subject probe type not trivially available, we
should still be able to hack around it in the runtime. Given the requested
virtual address, aat registration time we could walk the process address space,
find the inode & offset corresponding to that address (if any!), and place a
inode+offset uprobe there. (This doesn't help non-inode gaps in the address
space, alas.)
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug runtime/18714] bring back process.statement.absolute probes
2015-07-24 14:51 [Bug runtime/18714] New: bring back process.statement.absolute probes fche at redhat dot com
@ 2018-11-10 18:05 ` agentzh at gmail dot com
0 siblings, 0 replies; 2+ messages in thread
From: agentzh at gmail dot com @ 2018-11-10 18:05 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=18714
agentzh <agentzh at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |agentzh at gmail dot com
--- Comment #1 from agentzh <agentzh at gmail dot com> ---
We'll take a stab at implementing `process.statement(0xaddr)` first for
inode-based uprobes, with relative addresses in the executable files (including
DSO and PIE). This will pave a way to true DWARF-less probing (with the
existing @vma() facility which will get merge soon) as well as implementing our
own uretprobes without all the consequences from the kernel's uretprobes.
Messed up C stacks are really problematic for stack unwinding and resizable
stacks.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-11-10 18:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-24 14:51 [Bug runtime/18714] New: bring back process.statement.absolute probes fche at redhat dot com
2018-11-10 18:05 ` [Bug runtime/18714] " agentzh at gmail dot com
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).