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

valgrind 3.3.0 (tar.bz2) [4520Kb] - 11 December 2007.
For {x86,amd64,ppc32,ppc64}-linux.
md5: e5fc39755a714f36b7e5014c1c6d4748

You may want to look at the 3.3.0 release notes.

3.3.0 primarily contains tool enhancements: a restored and improved version of Helgrind (thread checker), majorly revamped version of Massif (space profiler), branch-mispredict profiling for Cachegrind, and new experimental tools (Omega and DRD). Also includes support for recent Linux distros (Fedora 8, openSUSE 10.3), scalability improvements (for gigabyte-sized applications), modestly improved documentation, fixes for 56 bug reports, experimental support for AIX5.3, and many minor refinements.


Valkyrie 1.2.0

valkyrie 1.2.0 (tar.bz2) [370Kb] - June 7 2006.
md5: 231982dc7063593f15ed2f93b85d0b2e

Valkyrie is a GUI for valgrind 3.0.0 or higher, as that was the first valgrind release to support XML output, which valkyrie requires. It also has an XML merging tool for Memcheck outputs (vk_logmerge). This tarball is known to build and work with valgrind-3.2.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-2007 Valgrind Developers

Best Viewed With A Browser