Information Source Code Documentation Contact How to Help Gallery

Current Releases

The complete source code, including documentation, is available as a tarball for the current release. For downloadable / browseable manual packages, go to the Documentation page. For older releases, see the Release Archive page.

If you would like to be notified when a new valgrind release is made, you can subscribe to the Valgrind announcements mailing list.

Release 3.3.1

valgrind 3.3.1 (tar.bz2) [4544Kb] - 4 June 2008.
For {x86,amd64,ppc32,ppc64}-linux.
md5: 0539e2fa4aadb2cd4ca4bba65b1fe8b5

You may want to look at the 3.3.1 release notes.

3.3.1 fixes a bunch of bugs in 3.3.0, adds support for glibc-2.8 based systems (openSUSE 11, Fedora Core 9), improves the existing glibc-2.7 support, and adds support for the SSSE3 (Core 2) instruction set.

3.3.1 builds and runs its regression tests on at least the following platforms, and probably more:

x86: RedHat 7.3, 8, 9, SuSE 10.1, 10.2, 11.0rc1, Fedora 9
amd64: SuSE 10.2, 11.0rc1, Ubuntu 8.04
ppc32: Fedora 8, 9
ppc64: Fedora 8, 9

Valkyrie 1.3.0

valkyrie 1.3.0 (tar.bz2) [365Kb] - June 30 2008.
md5: ec7069a23ec90670be74d3fc3a46f574

Valkyrie is a GUI for valgrind 3.3.0 or higher. It also has an XML merging tool for Memcheck outputs (vk_logmerge). This tarball is known to build and work with valgrind-3.3.0.

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.

Best Viewed With A Browser