|
From: Yeshurun, M. <mei...@in...> - 2005-08-07 09:13:15
|
The problem was solved simply by sending Valgrind's output to log files instead of standard output. (I'm using a PIE build of Valgrind 3.0 on a 64 bit platform.) Perhaps Valgrind and the child process were fighting over the same file descriptor. Thanks, Meir=20 -----Original Message----- From: Nicholas Nethercote [mailto:nj...@cs...]=20 Sent: Tuesday, August 02, 2005 4:54 PM To: Yeshurun, Meir Cc: val...@li... Subject: Re: [Valgrind-users] Effect of libc_freeres() on exit status of child process when running under Valgrind On Tue, 2 Aug 2005, Yeshurun, Meir wrote: > My program has a child process that produces the common invalid free > error because of libc_freeres(). Are you using --libc-freeres=3Dyes? > Can this cause the child process to return a failure exit status (even > if it returns a success exit status when the program is not run under > Valgrind)? Valgrind does not itself change the exit code of a program, so this is=20 unlikely. N |