I can't really think of a better way to tackle the problem... But I will make this one observation: If these underlying frameworks you depend on produce *thousands* of valgrind errors, do you really want to be depending on them?
(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.) Just my opinion, David On Fri, Jun 25, 2010 at 7:18 AM, Johny Jose <[email protected]> wrote: > Dear all, > > 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 ? > > Regards > Johny > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
