Current Releases

valgrind 3.4.1 (tar.bz2) [5183Kb] - 28 Feb 2009.
For {x86,amd64,ppc32,ppc64}-linux.
md5: b5f039dd2271aaf9ae570ab4116f87c7

You may want to look at the 3.4.1 release notes.

3.4.1 is a bug-fix release that fixes some regressions and assertion failures in debug info reading in 3.4.0, most notably incorrect stack traces on amd64-linux on older (glibc-2.3 based) systems. Various other debug info problems are also fixed. A number of bugs in the exp-ptrcheck tool introduced in 3.4.0 have been fixed.

In view of the fact that 3.4.0 contains user-visible regressions relative to 3.3.x, upgrading to 3.4.1 is recommended. Packagers are encouraged to ship 3.4.1 in preference to 3.4.0.

Valkyrie 1.4.0

valkyrie 1.4.0 (tar.bz2) [365Kb] - 21 Feb 2009.
md5: 9f0eb896e85485874566496dc1587139

Valkyrie is a GUI for the Valgrind 3.4.x releases. It also has an XML merging tool for Memcheck outputs (vk_logmerge). This tarball is known to build and work with valgrind-3.4.0.

This version of Valkyrie does not support the older Valgrind 3.3.x releases. If you need a GUI for Valgrind 3.3.x, instead use valkyrie 1.3.0 (tar.bz2) instead.

RPMs / Binaries

We do not distribute binaries or RPMs. The releases available on this website contain the source code and have to be compiled in order to be installed on your system. Many Linux distributions come with valgrind these days, so if you do not want to compile your own, go to your distribution's download site.

System Requirements

Programs running under Valgrind run significantly more slowly, and use much more memory -- e.g. more than twice as much as normal under the Memcheck tool. Therefore, it's best to use Valgrind on the most capable machine you can get your hands on.