Thanks Julian, I tried all of my tests again and there are no mixed up
lines. I should have listened to you the first time.
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.
Thanks,
Madhan.
On Wed, Jan 7, 2009 at 8:17 PM, Julian Seward <[email protected]> wrote:
>
> > Options used:
> > --log-file=/scratch/work/valgrind_check.pid%p
> > --leak-check=full
> > --leak-resolution=high
> > --undef-value-errors=yes
> > --track-fds=yes
> > --workaround-gcc296-bugs=yes
> > --error-limit=no
> > --num-callers=60
> > --run-libc-freeres=no
> > -v
> > --tool=memcheck
>
> You need --child-silent-after-fork=yes.
>
> 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
