With the parameter --valgrind-massif, the configure script sets
reasonable defaults that can be overridden as explained in
the documentation.
---
configure | 4 ++++
doc/developer.texi | 7 ++++---
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/configure b/configure
index 94804bd..f39a860 100755
--- a/configure
+++ b/configure
@@ -2211,6 +2211,10 @@ case "$toolchain" in
add_cflags -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)
target_exec_default="valgrind"
target_exec_args="--track-origins=yes --leak-check=full"
diff --git a/doc/developer.texi b/doc/developer.texi
index c3d0f20..58635f8 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
--
1.8.2.1
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
