|Information Source Code Documentation Contact How to Help Gallery|
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.10.1 (tar.bz2)
[11MB] - 25 November 2014.
You may want to look at the 3.10.1 release notes.
3.10.1 is a bug fix release. It fixes various bugs reported in 3.10.0 and backports fixes for all reported missing AArch64 ARMv8 instructions and syscalls from the trunk. If you package or deliver 3.10.0 for others to use, you might want to consider upgrading to 3.10.1 instead. See the release notes for details.
This release supports X86/Linux, AMD64/Linux, ARM/Linux, ARM64/Linux,PPC32/Linux, PPC64/Linux, PPC64BE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android (2.3 and later), X86/Android (4.0 and later), MIPS32/Android, X86/Darwin and AMD64/Darwin (Mac OS X 10.9 and, to a limited extent, 10.8).
valkyrie 2.0.0 (tar.bz2)
[260Kb] - 21 October 2010.
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.
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.
Copyright © 2000-2014 Valgrind™ Developers