[CMake] Custom memory checking result processing

[Bill Hoffman]

On 6/25/2010 10:16 AM, David Cole wrote:
> For the cmake valgrind dashboard, we use the script seen here:
> http://www.cdash.org/CDash/viewNotes.php?buildid=647028
>
> If you look at it, you will see that we list a bunch of tools that
> produce valgrind output that we are not interested in having show up on
> the CMake dashboard.
>
> (For example, /usr/bin/gcc and /usr/bin/c++ are in the list...)
>
> Then, we pass that to valgrind with the
> --trace-children-skip=${valgrind_skip} command line flag.
>
> Here's the catch: that's a custom build of valgrind that we have on that
> machine that understands this flag. I think Bill Hoffman developed the
> patch for that behavior and tried to submit it up to valgrind upstream,
> but there was much discussion and no action, if I recall correctly.
>

The patch has been accepted and is in valgrind.  It is a slight 
different format but does the same thing.  So, an SVN valgrind will have 
the new flag.    The other thing to note is that this stops all 
processing after that.  So, for example since make will call cmake, we 
allow make to be valgrind processed, and just add the suppression stuff 
I mentioned in my other email.

> Maybe Bill could chime in, or you could take up the question on
> valgrind's mailing list....?
>
No need to go on the valgrind list, should be there now.  I have not 
tested and really do need to upgrade our valgrind to try the official 
version of this feature...

-Bill