Here's another easy way to reproduce this bug. Note the difference in
PID's in valgrinds output:
[EMAIL PROTECTED] ~$ cat test.c
#include <sys/types.h>
#include <unistd.h>
int main( int argc, char **argv )
{
if( fork() > 0 )
sleep( 1 );
return 0;
}
[EMAIL PROTECTED] ~$ gcc -Wall -o test test.c
[EMAIL PROTECTED] ~$ valgrind --trace-children=no ./test
==14488== Memcheck, a memory error detector for x86-linux.
==14488== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==14488== Using valgrind-2.4.0, a program supervision framework for x86-linux.
==14488== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al.
==14488== For more details, rerun with: -v
==14488==
==14489==
==14489== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 1)
==14489== malloc/free: in use at exit: 0 bytes in 0 blocks.
==14489== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==14489== For counts of detected errors, rerun with: -v
==14489== No malloc'd blocks -- no leaks are possible.
==14488==
==14488== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 13 from 1)
==14488== malloc/free: in use at exit: 0 bytes in 0 blocks.
==14488== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==14488== For counts of detected errors, rerun with: -v
==14488== No malloc'd blocks -- no leaks are possible.
Marcel Moreaux <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
