|
From: David T. <twe...@ya...> - 2006-05-02 13:43:06
|
Hi, bit of a silly question: Running valgrind-3.1.0 on an Intel EM64T-thing (Fedora Core 5), even with an explicit --trace-children=no I get the following behaviour: I've got a program which launches other programs via double-forking. In particular, the parent fork()'s and waitpid()'s for the child. The child forks and terminates quickly -- after writing a couple of bytes ot a pipe -- with an _exit(0). And the grandchild does an exec() into another program proper. Running valgrind --tool=memcheck --trace-children=no program I get ERROR SUMMARY and LEAK SUMMARY data written for something with a process ID other than the main process each time I launch a program this way. It's not a real problem but it does comprise a signifcant proportion of my valgrind output to read through. Is there any simple call I can put into my code to stop valgrind writing output for child branch of the fork()? Many thanks for any insight, cheers, dave tweed ___________________________________________________________ Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. http://uk.mail.yahoo.com |