diff options
| author | Reinhard Tartler <siretart@tauware.de> | 2013-05-04 10:25:41 +0200 |
|---|---|---|
| committer | Reinhard Tartler <siretart@tauware.de> | 2013-05-04 12:17:51 +0200 |
| commit | b1ee8eec849f17fce2f411a297de9cbf2edaeb3a (patch) | |
| tree | 3f8118ac46f7578e0b9cb79b90affc9c95f3e341 /doc/developer.texi | |
| parent | 95e8ac60f8b7317ce23c648250fdc8fb68d65a07 (diff) | |
configure: Add basic valgrind-memcheck support
With the parameter --valgrind-memcheck, the configure script sets
reasonable defaults that can be overridden as explained in the
documentation.
The idea of using set_defaults is from Luca Barbato.
Diffstat (limited to 'doc/developer.texi')
| -rw-r--r-- | doc/developer.texi | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/developer.texi b/doc/developer.texi index 3d574e4428..c3d0f2065c 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -574,6 +574,18 @@ You can use the command @code{make lcov-reset} to reset the coverage measurements. You will need to rerun @code{make lcov} after running a new test. +@subsection Using Valgrind + +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. + +In case you need finer control over how valgrind is invoked, use the +@code{--target-exec='valgrind <your_custom_valgrind_options>} option in +your configure line instead. + @anchor{Release process} @section Release process |