diff options
| author | Luca Barbato <lu_zero@gentoo.org> | 2013-05-14 22:15:18 +0200 |
|---|---|---|
| committer | Luca Barbato <lu_zero@gentoo.org> | 2013-05-18 21:29:17 +0200 |
| commit | edfe609fc9466cbd4f847afac430545799a66e14 (patch) | |
| tree | aaf74f4fd6dde9a174e17423a00219b199f94e4c /doc/developer.texi | |
| parent | ed50673066956d6f2201a57c3254569f2ab08d9d (diff) | |
configure: Add basic valgrind-massif support
With the parameter --toolchain valgrind-massif, the configure
script sets reasonable defaults that can be overridden as explained
in the documentation.
Diffstat (limited to 'doc/developer.texi')
| -rw-r--r-- | doc/developer.texi | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/developer.texi b/doc/developer.texi index c3d0f2065c..58635f808f 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -578,9 +578,10 @@ new test. The configure script provides a shortcut for using valgrind to spot bugs related to memory handling. Just add the option -@code{--toolchain=valgrind-memcheck} to your configure line, and -reasonable defaults will be set for running FATE under the supervision -of the @strong{memcheck} tool of the valgrind suite. +@code{--toolchain=valgrind-memcheck} or @code{--toolchain=valgrind-massif} +to your configure line, and reasonable defaults will be set for running +FATE under the supervision of either the @strong{memcheck} or the +@strong{massif} tool of the valgrind suite. In case you need finer control over how valgrind is invoked, use the @code{--target-exec='valgrind <your_custom_valgrind_options>} option in |