Nathan Rittenhouse <[email protected]> writes: > Currently, I'm running the Catchconv Valgrind extension against > an application to generate a path constraint. The application in > question clones() several times and even has a clone() from inside of > a clone()'d thread/process. > > I added some debug message printing into Catchconv's main callback > function, ca_instrument(), using VG_(printf) and VG_(message). In the > case where there is only one clone(), the proper messages made it to > stderr/stdout. However, in the case where there are multiple clones > and chains of clones, only one of those process' messages ever made > it to stderr/stdout.
Valgrind has a couple options dealing with fork and exec: --trace-children=no|yes Valgrind-ise child processes (follow execve)? [no] --child-silent-after-fork=no|yes omit child output between fork & exec? [no] note that the defaults for both of them are "no". Have you tried running with these explicitly enabled? Cheers, -tom ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
