Bug 14706 - Support multiple target processes in stapdyn
Summary: Support multiple target processes in stapdyn
Status: NEW
Alias: None
Product: systemtap
Classification: Unclassified
Component: dyninst (show other bugs)
Version: unspecified
: P2 enhancement
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-11 19:21 UTC by Josh Stone
Modified: 2013-02-07 21:17 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Stone 2012-10-11 19:21:40 UTC
We should support multiple target processes in stapdyn.  This primarily means following fork/exec process children from the initial target, but it could also mean allowing multiple -c/-x targets, if we want.

We'll need shared memory between targets, at least for global variables (including per-thread stats memory, so anyone can aggregate).  Any events that are not process specific (e.g. begin, end, timers) can run in the stapdyn process, like they are now for the case with no target process.
Comment 1 Josh Stone 2013-01-18 02:54:30 UTC
There have been many commits as baby steps towards shared memory, but commit f4d70a33 is the first that's finally running across processes.  As planned, begin/end/timers are now running directly in stapdyn, while uprobes/utrace-like probes run in the target process.

Next is to follow fork/exec to really have multiple process targets.
Comment 2 Josh Stone 2013-02-07 21:17:25 UTC
Forks should work as of commits 72100304 and 964519ac.

Exec is started in commit b9babf95, but that still has issues to work out.