G'Day, On Wed, Feb 13, 2008 at 04:55:06PM -0500, Asif Iqbal wrote: > I am assuming you looked at DTT by Brendan Gregg which has a dtrace > script called dtruss..
dtruss follows syscalls (like truss -f), but not pid provider probes (like truss -u). dapptrace is more like truss -u, however I didn't code a follow mode. As Matthieu showed, it's possible to hack a solution using the system() call and the destructive pragma (which I believe is the best solution if you really must do this). When you want to track latencies across forked children, it's often possible to do so via the other providers - syscall, proc, sched, etc, and using progenyof(). Although, David's original script was tracing some malloc() family calls - which can only be currently traced directly via pid (a malloc USDT provider anyone?). David, the syscall provider can give you mmap(), munmap() and mprotect(), and progenyof() can follow children. It might be possible to infer some malloc(), calloc() and free() events via syscall brk() and vminfo probes. Brendan > On Feb 13, 2008 4:23 PM, David Weston <[EMAIL PROTECTED]> wrote: > > is it possible to follow a forked process with a D script? Would I have to > > spawn a second dscript to follow it since the probes may no be enabled for > > the forked process? > > > > > > > > -- > > This message posted from opensolaris.org > > _______________________________________________ > > dtrace-discuss mailing list > > [email protected] > > > > > > -- > Asif Iqbal > PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu > _______________________________________________ > dtrace-discuss mailing list > [email protected] -- Brendan [CA, USA] _______________________________________________ dtrace-discuss mailing list [email protected]
