Valgrind Home Information Source Code Documentation Contact How to Help Gallery

Supported Platforms


Current

Valgrind supports the following platforms:

  • x86/Linux: support is mature and almost complete.
  • AMD64/Linux: support is mature and almost complete. Note that AMD64 is just another name for x86-64, and that Valgrind works fine on Intel machines.
  • PPC32/Linux: support is new but fairly complete.
  • PPC64/Linux: support is new but fairly complete.
  • x86/Darwin (Mac OS X): support is new.
  • AMD64/Darwin (Mac OS X): support is new.
  • S390X/Linux: support is new in 3.7.0.
  • ARM/Linux support for ARMv7 is fairly complete.
  • ARM/Android support is new in 3.7.0.
  • MIPS32/Linux support is new in 3.8.0.

On Linux, you must be running kernel 2.6.X or later, and glibc 2.5.X or later. That covers the vast majority of installed systems at present. On Mac OS X you must be running 10.7.x or later.

For details of which distributions the current release (valgrind-3.10.1) builds and runs its regression tests on, see the release notes.

Out Of Tree

The following ports have been done and are maintained outside the Valgrind repository. Note that they may have varying levels of completeness, may not work reliably, and may target older versions of Valgrind.

  • x86/FreeBSD: Doug Rabson and others haved done a fairly complete port of Valgrind 3.X. The FreeBSD porting team actively maintains the port. Snapshots of the work in progress are at this FreeBSD page.

  • x86/NetBSD: Eric Auge, Kailash Sethuraman and Peter Bex are doing a port of Valgrind 3.X, available at this page.

  • x86/Solaris and x86/illumos: The port of Valgrind on Oracle Solaris and illumos has been developed since 2012 and is actively maintained by a collaborative effort of several people. The code is available at this page. A presentation about the port given at FOSDEM 2014 is available at this page.


Porting Plans

Valgrind 3.X has the infrastructure to support multiple platforms. A platform is a specific (CPU,OS) pairing, such as x86/Linux or AMD64/Linux.

Maintaining each port takes a lot of effort, more so than for most other programs. Valgrind is fragile due to the low-level nature of what it does. Also, each platform port has CPU-specific code, OS-specific code and platform-specific code, and testing all the combinations is difficult.

Because of this, we can only justify supporting platforms that are widely used. Unlike NetBSD or GCC, we are not interested in having Valgrind work on every platform in the known universe: the maintenance burden is too high. Therefore, porting Valgrind to different platforms is not simply a technical exercise: you also need to make a convincing case that the effort will be worth it, and that the port will be supported properly, at least in the foreseeable future.

Windows is not under consideration because porting to it would require so many changes it would almost be a separate project. (However, Valgrind + Wine can be made to work with some effort.) Also, non-open-source OSes are difficult to deal with; being able to see the OS and associated (libc) source code makes things much easier. However, Valgrind is quite usable in conjunction with Wine, which means that it is possible to run Windows programs under Valgrind with some effort.

This message states our porting rationale. As ever we retain a flexible approach, and are interested in hearing your comments/porting needs if you have any.



Bad, Bad Bug!

Copyright © 2000-2014 Valgrind™ Developers

Hosting kindly donated by Mythic Beasts