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.


Valgrind 3.12.0

valgrind 3.12.0 (tar.bz2) [12MB] - 20 October 2016.
For {x86,amd64,arm32,arm64,ppc32,ppc64le,ppc64be,s390x,mips32,mips64}-linux, {arm32,arm64,x86,mips32}-android, {x86,amd64}-solaris, {x86,amd64}-darwin (Mac OS X 10.10, with limited support for 10.11 and 10.12) and preliminary support for tilegx-linux.
md5: 6eb03c0c10ea917013a7622e483d61bb

3.12.0 is a feature release with many improvements and the usual collection of bug fixes. This release adds support for POWER ISA 3.0, improves instruction set support on ARM32, ARM64 and MIPS, and provides support for the latest common components (kernel, gcc, glibc). There are many smaller refinements and new features. See the release notes for details.


Valkyrie 2.0.0

valkyrie 2.0.0 (tar.bz2) [260Kb] - 21 October 2010.
md5: a411dfb803f548dae5f988de0160aeb5

Valkyrie is a Qt4-based GUI for the Valgrind 3.6.x and 3.7.x series, that works for the Memcheck and Helgrind tools. It also has an XML merging tool for Memcheck outputs (vk_logmerge). This tarball is known to build and work with valgrind-3.6.0 and valgrind-3.7.0.

This version of Valkyrie does not support any version of Valgrind prior to 3.6.0. If you want to use Valkyrie with an older Valgrind version, we recommend you instead upgrade your Valgrind to 3.6.0 and use this version of Valkyrie.


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-2016 Valgrind™ Developers

Hosting kindly donated by Mythic Beasts