For the cmake valgrind dashboard, we use the script seen here:<br><a href="http://www.cdash.org/CDash/viewNotes.php?buildid=647028">http://www.cdash.org/CDash/viewNotes.php?buildid=647028</a><br><br>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.<br>
<br>(For example, /usr/bin/gcc and /usr/bin/c++ are in the list...)<br><br>Then, we pass that to valgrind with the --trace-children-skip=${valgrind_skip} command line flag.<br><br>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.<br>
<br>Maybe Bill could chime in, or you could take up the question on valgrind's mailing list....?<br><br><br>HTH,<br>David<br><br><br>On Fri, Jun 25, 2010 at 9:44 AM, Johny Jose <<a href="mailto:Johny.Jose@cern.ch">Johny.Jose@cern.ch</a>> wrote:<br>
><br>> The frameworks in question are a necessary evil, we cannot do without them, time and habit will not allow us to work with anything else i guess. Well i guess i will have to try it out and see what comes of it, will let u know how successful it is.<br>
><br>> Regards,<br>> Johny<br>><br>><br>> -----Original Message-----<br>> From: Marcel Loose [mailto:<a href="mailto:loose@astron.nl">loose@astron.nl</a>]<br>> Sent: Fri 6/25/2010 2:30 PM<br>> To: <a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a><br>
> Cc: Johny Jose; <a href="mailto:cmake@cmake.org">cmake@cmake.org</a><br>> Subject: Re: [CMake] Custom memory checking result processing<br>><br>> Well, I sort of ran into exactly the same problem that Johny describes.<br>
> I devoted two mails on this issue to the CMake list --<br>> <a href="http://www.mail-archive.com/cmake@cmake.org/msg26858.html">http://www.mail-archive.com/cmake@cmake.org/msg26858.html</a><br>> <a href="http://www.mail-archive.com/cmake@cmake.org/msg29155.html">http://www.mail-archive.com/cmake@cmake.org/msg29155.html</a> -- but got no<br>
> response on either of them.<br>><br>> In my case 'bash' is producing quite some noise; wouldn't want to call<br>> 'bash' flaky, though. But even if that weren't the case: you don't want<br>
> to memory check your framework every time you run a test, only the<br>> program under test.<br>><br>> There must be a better way to solve this, right?<br>><br>> Best regards,<br>> Marcel Loose.<br>><br>
> On Fri, 2010-06-25 at 07:47 -0400, David Cole wrote:<br>> > I can't really think of a better way to tackle the problem...<br>> ><br>> ><br>> > But I will make this one observation:<br>> > If these underlying frameworks you depend on produce *thousands* of<br>
> > valgrind errors, do you really want to be depending on them?<br>> ><br>> ><br>> > (Serious question, not trying to be flippant... It would make me very<br>> > nervous to depend on a framework that has more than a handful of<br>
> > valgrind issues: and each issue would have to be something that I was<br>> > convinced did not have a high likelihood of occurring in real world<br>> > usage scenarios.)<br>> ><br>> ><br>
> ><br>> ><br>> > Just my opinion,<br>> > David<br>> ><br>> ><br>> ><br>> > On Fri, Jun 25, 2010 at 7:18 AM, Johny Jose <<a href="mailto:Johny.Jose@cern.ch">Johny.Jose@cern.ch</a>><br>
> > wrote:<br>> > Dear all,<br>> > <br>> > I am using valgrind to debug a framework which depends on<br>> > several other underlying frameworks to function properly. As a<br>
> > result my memory checking turns up thousands of errors. I only<br>> > want to see errors that arise from my framework. This is<br>> > figured can be done by simply looking for a few regular<br>
> > expressions in the stack trace. Right now i am planning on<br>> > creating a custom perl script which i will use as the<br>> > memchecker instead of valgrind and send its output to CDash.<br>
> > Suppression files don't seem feasible as they don't have any<br>> > sort of RegEx support and i have too many errors to list in a<br>> > file creating ridiculously large logs and suppression files. I<br>
> > was wondering is there any better way to tackle this problem ?<br>> > <br>> > Regards<br>> > Johny<br>> > <br>> > <br>> > <br>
> > <br>> > _______________________________________________<br>> > Powered by <a href="http://www.kitware.com">www.kitware.com</a><br>> > <br>> > Visit other Kitware open-source projects at<br>
> > <a href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br>> > <br>> > Please keep messages on-topic and check the CMake FAQ at:<br>
> > <a href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a><br>> > <br>> > Follow this link to subscribe/unsubscribe:<br>> > <a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a><br>
> ><br>> ><br>> > _______________________________________________<br>> > Powered by <a href="http://www.kitware.com">www.kitware.com</a><br>> ><br>> > Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br>> ><br>> > Please keep messages on-topic and check the CMake FAQ at:<br>> <a href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
> ><br>> > Follow this link to subscribe/unsubscribe:<br>> > <a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a><br>><br>><br>><br><br>