Browse Source

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.
tags/n2.0
Luca Barbato 12 years ago
parent
commit
edfe609fc9
2 changed files with 8 additions and 3 deletions
  1. +4
    -0
      configure
  2. +4
    -3
      doc/developer.texi

+ 4
- 0
configure 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"


+ 4
- 3
doc/developer.texi 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
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 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


Loading…
Cancel
Save