Thanks Julian. That clearly answers my question. In my application I have
seen
that its always a fork and exec, with negligible code in between them.
Let me go back and check if there is a functionality with only a fork and no
exec.
Thanks again,
Madhan.
On Mon, Jan 12, 2009 at 12:46 AM, Julian Seward <[email protected]> wrote:
>
> > Let me make sure I understand it clearly. You have mentioned that,
> > --child-silent-after-fork option suppresses all output between a fork and
> > exec. The %p specifier in the --log-file option, I thought is used to
> give
> > every pid its own file and to avoid the jumbling up in log files. So fork
> > does not create a new log file even with %p.
>
> The logfile is created at exec time, not when fork happens. So that means
> that in between the fork and the exec, the child process is writing to the
> same file as the parent. --child-silent-after-fork=yes makes the child be
> quiet exactly in the time between fork and exec. After the child does
> exec, it creates a new log file with its own PID and so everything goes
> back to normal after that.
>
> J
>
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
