Variants and Patches

Several other Valgrind tools have been created. Some of these can plug directly into an existing Valgrind installation, but some require downloading a whole Valgrind distribution which contains a specially modified core. Please note that some of these are experimental, and may not work 100%.

Nick Nethercote has built several experimental tools: a Bounds Checker, a Signal-Handler Checker, and a Data Flow Tracer. He also has an experimental Valgrind distribution that has an interactive command line.

Jeremy Fitzhardinge has several patches, mostly to do with threading. His patches are regularly merged with the CVS head; this set represents the currently unmerged patches.

Robert Walsh has some useful patches: one adds watchpoints on memory locations, the other adds support for pool-based allocators.

Adam Gundy <arg at cyberscience com> supplied a variant of the 20031012 stable release that is capable of running Wine on Valgrind. A big thanks to him.

Wine: valgrind 20031012-wine (tar.bz2) [697Kb] - Oct 12 2003
md5: ebe1641b4873ec30dd013b6b618f5f90

This is a variant of the 20031012 stable release. It makes it possible to run Wine on Valgrind, and so to debug Windows applications with Valgrind. See README_WINE_FOLKS in the tarball for details.

Note: only use this -wine variant if you want to valgrindify Wine and apps running on it. For "normal" Linux applications, use the standard valgrind version.

Valgrind 20031012-wine should be used with a recent CVS version of Wine. Provided you have the PDB files for executables and DLLs, valgrind will give stack traces for MSVC compiled code. Multi-threaded programs are fully supported. Leak checking does not work at the moment.

Vince Weaver has written three tools: a cache tool trace generator, a SimPoint data generator, and a TAXI-compatible stream generator. (TAXI decodes pre-decoded x86 instruction

Michael Meeks has written Iogrind, a prototype I/O profiling tool.