On Wed, 2008-04-30 at 17:51 +0200, [EMAIL PROTECTED] wrote:
> > Well, if you're really talking about re-inserting probes into a
> > completely new image (after the exec)
> > than I consider DTrace to be doing exactly the right thing -- these
> > are brand new probes so they have to be reinserted.
>
> I am dealing with same problem as Bayard trying to trace child processes.
> >From Roman's answer I do not exactly know if it is possible or not.
It is possible via the system action that would reinsert the probes
into the brand new PID.
> What do you
> mean with "....DTrace to be doing exactly the right thing -- these are brand
> new
> probes so they have to be reinserted....."?? I've tried to trace my test
> program which spawns
> child and I really wasn't able to see any trace output for that child from
> pid provider.
That's why I asked my question -- I can agree that if the process simply
forks and does NOT do an exec DTrace can be expected (although not
required) to keep the probes around. Once exec is done -- all bets are
off anyway. You have to reinsert the probes. Regardless of whether
you do it manually (via system("dtrace...");) or you have your
dynamic PID provider. Works needs to be done. Unlike with pure forks
where in fact, work is done to *remove* probes from the newborn child.
> However I really do not know if it is technically possible to create "dynamic
> pid provider" :-)
Well, start hacking, then ;-)
Thanks,
Roman.
_______________________________________________
dtrace-discuss mailing list
[email protected]
