[Valgrind-developers] Trace child black list patch

[Bill H. <bil...@ki...>]

I would like to bring this issue up again.  The bug report is here:

http://bugs.kde.org/show_bug.cgi?id=148932

The blog is here:

http://blog.mozilla.com/nnethercote/2009/04/30/making-valgrind-easier-to-use-with-multi-process-programs/


I think this may have become too complicated.  Is this perhaps a case of 
"The perfect is the enemy of the good."   I think my simple black list 
approach works very well.  Here is the use case:

1. run valgrind with --trace-children
2. look at output, black list stuff you don't want, and goto step 1.
3. it is working great now, setup nightly regression test with black list.

This version of a patch works great an is done:
http://www.nabble.com/ping-on-bug-report-to18223378.html#a22091908

I really don't see it as a bad thing or that hard to support.

I think it was generally something that Julian liked:
http://www.nabble.com/ping-on-bug-report-to18223378.html#a22091908

I did the cleanup that was requested...   It would be very useful to me 
so that I would not have to keep applying the patch to valgrind on each 
update....


Thanks.

-Bill