diff options
| author | Michael Niedermayer <michaelni@gmx.at> | 2013-05-05 12:47:19 +0400 |
|---|---|---|
| committer | Michael Niedermayer <michaelni@gmx.at> | 2013-05-05 12:47:19 +0400 |
| commit | 4451be5ce1fc0517e566e005b6fb8f30ee2e3351 (patch) | |
| tree | e7b6444b42906582075b0a20a5093dcb6ac35ac4 /doc/developer.texi | |
| parent | 336ffb837705810682423b4d411c20170e56b923 (diff) | |
| parent | b1ee8eec849f17fce2f411a297de9cbf2edaeb3a (diff) | |
Merge commit 'b1ee8eec849f17fce2f411a297de9cbf2edaeb3a'
* commit 'b1ee8eec849f17fce2f411a297de9cbf2edaeb3a':
configure: Add basic valgrind-memcheck support
Conflicts:
configure
Merged-by: Michael Niedermayer <michaelni@gmx.at>
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 d5580d1543..90885eeaaa 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -604,6 +604,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 |