On Wed, Apr 30, 2008 at 05:51:15PM +0200, [EMAIL PROTECTED] wrote: > I am dealing with same problem as Bayard trying to trace child processes. > [...] > However I really do not know if it is technically possible to create "dynamic > pid provider" :-)
The way I've done this in the past is to use syscall or proc probes to stop() the child process, followed by a system() action to start a new instance of DTrace to trace the new process. I don't see how to create a "dynamic pid provider" without stopping the new child process to give the pid provider a chance to get a proc handle to it and do all that it has to do to setup pid provider probes. Which means that a "dynamic pid provider" would have to be destructive. But, yeah, it'd be nice to not have to system() a new DTrace instance. In Java I think you could certainly do it by using the Java interfaces to DTrace. But if you're using dtrace(1M) then yes, you have to start a new instance. Nico -- _______________________________________________ dtrace-discuss mailing list [email protected]
