Valgrind Home 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.4.0

valgrind 3.4.0 (tar.bz2) [5175Kb] - 2 Jan 2009.
For {x86,amd64,ppc32,ppc64}-linux.
md5: 1b0fe1219e1a583ff8c2db54ed2265e6

You may want to look at the 3.4.0 release notes.

3.4.0 is a feature release with many improvements and the usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux. Support for recent distros (using gcc 4.4, glibc 2.8 and 2.9) has been added.

3.4.0 brings some significant tool improvements. Memcheck can now report the origin of uninitialised values, the thread checkers Helgrind and DRD are much improved, and we have a new experimental tool, exp-Ptrcheck, which is able to detect overruns of stack and global arrays. There are many other smaller refinements and improvements.


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 and 3.3.1. 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.

This version of Valkyrie does not support the new Valgrind 3.4.0 release. However, we plan to release a new Valkyrie version (1.4.0) on or before 9 Jan 2009, which does support Valgrind 3.4.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.



Bad, Bad Bug!

Copyright © 2000-2009 Valgrind Developers

Best Viewed With A Browser