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
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
Message-
From: Marcel Loose [mailto:lo...@astron.nl]
Sent: Fri 6/25/2010 2:30 PM
To: david.c...@kitware.com
Cc: Johny Jose; cmake@cmake.org
Subject: Re: [CMake] Custom memory checking result processing
Well, I sort of ran into exactly the same problem that Johny describes.
I devoted two mails
On 6/25/2010 7:47 AM, David Cole wrote:
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
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
but i do
know which errors i do need. It would be a really great feature to add to
valgrind.
Regards,
Johny
-Original Message-
From: cmake-boun...@cmake.org on behalf of Bill Hoffman
Sent: Fri 6/25/2010 4:17 PM
To: cmake@cmake.org
Subject: Re: [CMake] Custom memory checking result
