Here
is what I can say from my experience:
purify - very nice, mostly stable.
needs at least linking, and while linking it can fail on some unusual library +
it uses embedded path as the first priority while searching for the library -
this particular feature caused some problem since libraries are found in places
where you don't intend them to be found.
Insure++ - at least our version was
buggy - it didn't work. you need to compile with it... but it checks your source
while compiling so it can find a problem (obvious problem) even before running
anything...
valgrind - no compilation, no linking.
Eats a lot of memory - thus you are limited in number of errors you can
report and you need to write suppression files to get to the real
trouble point... Catches everything that can be caught using such a
tool.
Thanks,
Gregory.
-----Original Message-----
From: Michael Sternberg [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 31, 2002 12:32 PM
To: linux-il (E-mail)
Subject: RE: Valgrind (was: KDE 3.0.2 RPM packages)
Other commercial tools like Insure++ for example ?
-- -----Original Message-----
-- From: Guy Baruch [mailto:[EMAIL PROTECTED]]
-- Subject: Re: Valgrind (was: KDE 3.0.2 RPM packages)
--
-- how does it compare with rational's purify tool ?
-- or any other such commercial tool ?
--
-- Kovriga, Gregory wrote:
--
-- >I tried it on a real project (we were porting from HP to Linux and it turned
-- >out that Linux isn't so forgiving as HP when talking about memory :)
-- >It was very helpful!
-- >
