Valgrind 1.0.0 Released

Anonymous Lazy Boy writes "Yesterday saw the official release of Valgrind 1.0.0. Valgrind is a C/C++ programmer's dream come true: effortless memory allocation checking, uninitialized memory access, leaks etc. Purify for Linux has arrived, only better: contrary to its commercial (non-Linux) sibling, checking is performed directly on the executable, no re-linking necessary. The technology behind Valgrind is highly fascinating and explained down to the very gory details in the documentation."

Comments

Re:BACKDOOR in Valgrind - Please Read

[michael]

Please don't feed the trolls. All the posts claiming a backdoor in Valgrind and supposedly responding to each other ("Hey, I found it too!" "Me too!" "Here's what I got!") were all posted by the same person.

Re:Any reviews?

[Charles Kerr]

I've been using Valgrind on Pan, which is multithreaded, and it works fine. Maybe given more time I'll find features that I miss from Purify, but for now I'm very happy.

Things I like better in Valgrind:

• Valgrind works on Linux.
• Valgrind doesn't require instrumenting each object file and library at build time. (This is a biggie)
• Valgrind's run-time options are more flexible.
• Valgrind works with both gcc 2 and 3.
• Valgrind seems to run faster than Purify. (Different hardware and OSes, so this is a guess.)
• Valgrind doesn't have a Motif GUI. ;)
• Valgrind doesn't have an insane, broken license manager.
• Valgrind's technical support is better. (Yes, I've dealt with both.)
• Valgrind doesn't cost $2,364 per seat.

Things I like better in Purify:

• Purify can handle static libraries.
• Purify makes it easier to disable errors/warnings from libraries out of your scope.
• Valgrind doesn't work on Solaris, so I'm stuck with Purify for my day job. :)