Peter Shoults wrote:
I suspect it is to stop the child process before it goes and does
whatever it is that we might want to capture.
right - not everything "in" dtrace happens synchronously (ie not all
actions are executed at the time the probe fires - an example for that are
the repeated reports of "I see hex numbers instead of symbols reported"),
and stop makes sure the child process doesn't go and do all the interesting
work before dtrace gets instrumentation in place - or so I understand it.
Michael
--
Michael Schuster http://blogs.sun.com/recursion
Recursion, n.: see 'Recursion'
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
