1
0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2025-01-13 21:28:01 +02:00

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.
This commit is contained in:
Luca Barbato 2013-05-14 22:15:18 +02:00
parent ed50673066
commit edfe609fc9
2 changed files with 8 additions and 3 deletions

4
configure vendored
View File

@ -2211,6 +2211,10 @@ case "$toolchain" in
add_cflags -fsanitize=thread -pie add_cflags -fsanitize=thread -pie
add_ldflags -fsanitize=thread -pie add_ldflags -fsanitize=thread -pie
;; ;;
valgrind-massif)
target_exec_default="valgrind"
target_exec_args="--alloc-fn=av_malloc --alloc-fn=av_mallocz"
;;
valgrind-memcheck) valgrind-memcheck)
target_exec_default="valgrind" target_exec_default="valgrind"
target_exec_args="--track-origins=yes --leak-check=full" target_exec_args="--track-origins=yes --leak-check=full"

View File

@ -578,9 +578,10 @@ new test.
The configure script provides a shortcut for using valgrind to spot bugs The configure script provides a shortcut for using valgrind to spot bugs
related to memory handling. Just add the option related to memory handling. Just add the option
@code{--toolchain=valgrind-memcheck} to your configure line, and @code{--toolchain=valgrind-memcheck} or @code{--toolchain=valgrind-massif}
reasonable defaults will be set for running FATE under the supervision to your configure line, and reasonable defaults will be set for running
of the @strong{memcheck} tool of the valgrind suite. 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 In case you need finer control over how valgrind is invoked, use the
@code{--target-exec='valgrind <your_custom_valgrind_options>} option in @code{--target-exec='valgrind <your_custom_valgrind_options>} option in