Introduction to Valgrind

Valgrind is an instrumentation framework for building dynamic analysis tools. There are Valgrind tools that can automatically detect many memory management and threading bugs, and profile programs in detail. Valgrind can also be used to build new tools.

This package is known to build and work properly using an LFS-8.1 platform.

Package Information

Valgrind Dependencies


BIND-9.11.2 or BIND Utilities-9.11.2 (for tests), Boost-1.64.0, GDB-8.0 (for tests), LLVM-4.0.1 (with Clang), and Which-2.21 (for tests)

User Notes:

Installation of Valgrind

Install Valgrind by running the following commands:

sed -i 's|/doc/valgrind||' docs/ &&

./configure --prefix=/usr \
            --datadir=/usr/share/doc/valgrind-3.13.0 &&


To run the tests for this package, valgrind requires a version of the /lib/ (or later) library with debugging symbols present. Normally in LFS these debugging symbols are stripped at the end of Chapter 6. To get this library, glibc must be rebuilt with the current glibc version using the same compiler that was used to build LFS. The can then be renamed to and copied to /lib. Then a symlink needs to be changed:

ln -sfv /lib/

Adjust the above instruction as needed for a 32-bit system or for a different version of glibc.

In addition, other glibc libraries with debugging symbols present may be needed for some tests.

To test the results, issue: make regtest. The tests may hang forever if GDB-8.0 is not installed. Some tests are known to hang also, depending on the version of glibc. Problematic tests can be disabled by changing the prereq: line in the corresponding .vgtest file to prereq: false. For example:

sed -e 's@prereq:.*@prereq: false@' \
    -i {helgrind,drd}/tests/pth_cond_destroy_busy.vgtest


The OpenMP tests are skipped if libgomp has been compiled with --enable-linux-futex (the default). If needed, just recompile the libgomp library from the gcc build tree, passing --disable-linux-futex to configure, storing the library to some place and changing the link from /usr/lib/ to point to the new library.

Now, as the root user:

make install

Command Explanations

sed -i ... docs/ : This sed provides for installing the documentation in a versioned directory.


Installed Programs: callgrind_annotate, callgrind_control, cg_annotate, cg_diff, cg_merge, ms_print, valgrind, valgrind-di-server, valgrind-listener, and vgdb
Installed Library: libcoregrind-<Arch>-linux.a, libreplacemalloc_toolpreload-<Arch>-linux.a, libvex-<Arch>-linux.a, libvexmultiarch-amd64-linux.a, vgpreload_core-<Arch>, vgpreload_drd-<Arch>, vgpreload_exp-dhat-<Arch>, vgpreload_exp-sgcheck-<Arch>, vgpreload_helgrind-<Arch>, vgpreload_massif-<Arch>, and vgpreload_memcheck-<Arch>, where <Arch> is x86 or amd64
Installed Directories: /usr/lib/valgrind, /usr/include/valgrind, and /usr/share/doc/valgrind-3.13.0

Short Descriptions


is a program for debugging and profiling Linux executables.


takes an output file produced by the Valgrind tool Callgrind and prints the information in an easy-to-read form.


controls programs being run by the Valgrind tool Callgrind.


is a post-processing tool for the Valgrind tool Cachegrind.


compares two Cachegrind output files.


merges multiple Cachegrind output files into one.


takes an output file produced by the Valgrind tool Massif and prints the information in an easy-to-read form.


is a server that reads debuginfo from objects stored on a different machine.


listens on a socket for Valgrind commentary.


is an intermediary between Valgrind and GDB or a shell.

Last updated on 2017-08-23 21:43:54 -0700