|
From: Bill H. <bil...@ki...> - 2009-06-22 17:14:55
|
Nicholas Nethercote wrote: > ---------- Forwarded message ---------- > From: Michael Sweet <ms...@ap...> > Date: Fri, Apr 24, 2009 at 8:41 AM > Subject: Re: [Valgrind-developers] ping on bug report > To: Nicholas Nethercote <n.n...@gm...> > > > On Apr 23, 2009, at 3:24 PM, Nicholas Nethercote wrote: > > ... > > (If anyone else has relevant use-cases they would encounter, please speak up!) > > FWIW, the CUPS "make test" target uses --trace-children=yes when > running with valgrind specifically so we can test all of the child > processes (print filters, generally) in their "native" environment > when run from CUPS - we wouldn't run in any other mode. > For the rest of the software I've run through valgrind (maybe a couple > dozen all together), I can only think of 1 case that I specifically > didn't want to trace children - EPM, which runs the corresponding > package maker program after creating all of the format-specific > support files/directories. Just curious as to the status of this? It is very useful to me, but it makes it hard for me to upgrade valgrind as I have to apply the patch each time. Thanks. -Bill |