I can't really think of a better way to tackle the problem...<div><br></div><div>But I will make this one observation:</div><div>If these underlying frameworks you depend on produce *thousands* of valgrind errors, do you really want to be depending on them?<br>
<br></div><div>(Serious question, not trying to be flippant... It would make me very nervous to depend on a framework that has more than a handful of valgrind issues: and each issue would have to be something that I was convinced did not have a high likelihood of occurring in real world usage scenarios.)</div>
<div><br></div><div><br></div><div>Just my opinion,</div><div>David</div><div><br></div><div><br><div class="gmail_quote">On Fri, Jun 25, 2010 at 7:18 AM, Johny Jose <span dir="ltr"><<a href="mailto:Johny.Jose@cern.ch">Johny.Jose@cern.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<p><font size="2">Dear all,<br>
<br>
I am using valgrind to debug a framework which depends on several other underlying frameworks to function properly. As a result my memory checking turns up thousands of errors. I only want to see errors that arise from my framework. This is figured can be done by simply looking for a few regular expressions in the stack trace. Right now i am planning on creating a custom perl script which i will use as the memchecker instead of valgrind and send its output to CDash. Suppression files don't seem feasible as they don't have any sort of RegEx support and i have too many errors to list in a file creating ridiculously large logs and suppression files. I was wondering is there any better way to tackle this problem ?<br>
<br>
Regards<br>
Johny<br>
</font>
</p>
</div>
<br>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">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" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br></div>