What I mean to ask is will PID provider trace child processes forked by the
parent process?
--- On Wed, 11/5/08, Angelo Rajadurai <[EMAIL PROTECTED]> wrote:
> From: Angelo Rajadurai <[EMAIL PROTECTED]>
> Subject: Re: [dtrace-discuss] truss "-fall" equivalent in DTrace
> To: [EMAIL PROTECTED]
> Cc: dtrace-discuss@opensolaris.org
> Date: Wednesday, November 5, 2008, 2:52 PM
> Change $1 to $target!
>
> (ie)
>
> ./sample.d -c "a.out"
> pid$target::somefunctionname:entry
> {
> printf("%s is called by %d",probefunc, tid);
> }
>
> In case you want to find the funcstions of a running
> process (say pid 1234)
> you have two options.
>
> ./sample.d --p 1234
> pid$target::somefunctionname:entry
> {
> printf("%s is called by %d",probefunc, tid);
> }
>
> or
> ./sample.d 1234
> pid$1::somefunctionname:entry
> {
> printf("%s is called by %d",probefunc, tid);
> }
>
>
> HTHs
>
> Angelo
>
> On Nov 5, 2008, at 5:21 AM, [EMAIL PROTECTED] wrote:
>
> > I have an executable. When I attach a truss, we have
> to give $truss -o truss.out -fall ./a.out. It shows all
> system calls made by this program and all the child
> processes it forks.
> >
> > Where as if I am using a DTrace script I am not able
> to do it.
> >
> > ./sample.d -c "a.out"
> > pid$1::somefunctionname:entry
> > {
> > printf("%s is called by %d",probefunc,
> tid);
> > }
> >
> >
> >
> >
> > _______________________________________________
> > dtrace-discuss mailing list
> > dtrace-discuss@opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
