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.5.0

valgrind 3.5.0 (tar.bz2) [5482Kb] - 19 Aug 2009.
For {x86,amd64,ppc32,ppc64}-linux and x86-Darwin (Mac OS X).
md5: f03522a4687cf76c676c9494fcc0a517

You may want to look at the 3.5.0 release notes.

3.5.0 is a feature release with many significant improvements and the usual collection of bug fixes. The main improvement is that Valgrind now works on Mac OS X.

This release supports X86/Linux, AMD64/Linux, PPC32/Linux, PPC64/Linux and X86/Darwin (Mac OS X). Support for recent distros and toolchain components (glibc 2.10, gcc 4.5) has been added.


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.

This version of Valkyrie also does not support the newer Valgrind 3.5.0 release. We plan to release a 3.5.0-compatible version of Valkyrie in the near future.


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