Home
last modified time | relevance | path

Searched full:valgrind (Results 1 – 25 of 803) sorted by relevance

12345678910>>...33

/external/strace/m4/
Dax_valgrind_check.m412 # AX_VALGRIND_CHECK checks whether Valgrind is present and, if so, allows
13 # running `make check` under a variety of Valgrind tools to check for
19 # the value of the --enable-valgrind option, which defaults to being
20 # enabled if Valgrind is installed and disabled otherwise. Individual
21 # Valgrind tools can be disabled via --disable-valgrind-<tool>, the
27 # LOG_COMPILER system, the $(VALGRIND) variable can be used within the
28 # shell scripts to enable Valgrind, as described here:
30 # https://www.gnu.org/software/gnulib/manual/html_node/Running-self_002dtests-under-valgrind.ht…
45 # This results in a "check-valgrind" rule being added to any Makefile.am
47 # configured with --enable-valgrind). Running `make check-valgrind` in
[all …]
/external/libabigail/autoconf-archive/
Dax_valgrind_check.m413 # AX_VALGRIND_CHECK checks whether Valgrind is present and, if so, allows
14 # running `make check` under a variety of Valgrind tools to check for
20 # the value of the --enable-valgrind option, which defaults to being
21 # enabled if Valgrind is installed and disabled otherwise. Individual
22 # Valgrind tools can be disabled via --disable-valgrind-<tool>, the
28 # LOG_COMPILER system, the $(VALGRIND) variable can be used within the
29 # shell scripts to enable Valgrind, as described here:
31 # https://www.gnu.org/software/gnulib/manual/html_node/Running-self_002dtests-under-valgrind.ht…
46 # This results in a "check-valgrind" rule being added to any Makefile.am
48 # configured with --enable-valgrind). Running `make check-valgrind` in
[all …]
/external/libyuv/files/tools_libyuv/valgrind/
Dlibyuv_tests.sh14 # - The locate_valgrind.sh of Chromium's Valgrind scripts dir is used to locate
15 # the Valgrind framework install. If it fails a fallback path is used instead
16 # (../../chromium/src/third_party/valgrind/linux_x64) and a warning message
19 # - Chromium's Valgrind scripts directory is added to the PYTHONPATH to make it
26 # tools_libyuv/valgrind/libyuv_tests.sh --tool memcheck
28 # tools_libyuv/valgrind/libyuv_tests.sh --tool=memcheck
51 # For libyuv, we'll use the locate_valgrind.sh script in Chromium's Valgrind
52 # scripts dir to locate the Valgrind framework install
53 CHROME_VALGRIND_SCRIPTS=$THISDIR/../../tools/valgrind
60 CHROME_VALGRIND=../../src/third_party/valgrind/linux_x64
[all …]
Dlocate_valgrind.sh11 # Prints a path to Valgrind binaries to be used for Chromium.
12 # Select the valgrind from third_party/valgrind by default,
18 # User may use their own valgrind by giving its path with CHROME_VALGRIND env.
50 # The binaries should be in third_party/valgrind
51 # (checked out from deps/third_party/valgrind/binaries).
52 CHROME_VALGRIND="$THISDIR/../../third_party/valgrind/$PLATFORM"
64 if ! test -x $CHROME_VALGRIND/bin/valgrind
66 echo "Oops, could not find Valgrind binaries in your checkout." >&2
68 echo " http://dev.chromium.org/developers/how-tos/using-valgrind/get-valgrind" >&2
Dvalgrind.sh11 # This is a small script for manually launching valgrind, along with passing
14 # $ sh ./tools/valgrind/valgrind.sh ./out/Debug/chrome
18 # That's the script used by the valgrind buildbot.
23 RUN_COMMAND="valgrind"
77 echo "Using valgrind binaries from ${CHROME_VALGRIND}"
82 # Valgrind binary.
83 export VALGRIND_LIB="$CHROME_VALGRIND/lib/valgrind"
84 export VALGRIND_LIB_INNER="$CHROME_VALGRIND/lib/valgrind"
94 # GTEST_DEATH_TEST_USE_FORK=1: make gtest death tests valgrind-friendly
96 # When everyone has the latest valgrind, we might want to add
Dchrome_tests.sh17 # tools/valgrind/chrome_tests.sh --tool memcheck
19 # tools/valgrind/chrome_tests.sh --tool=memcheck
54 echo "Using valgrind binaries from ${CHROME_VALGRIND}"
58 # Valgrind binary.
59 export VALGRIND_LIB="$CHROME_VALGRIND/lib/valgrind"
60 export VALGRIND_LIB_INNER="$CHROME_VALGRIND/lib/valgrind"
67 echo "Cleanup /tmp from Valgrind stuff"
69 -name "vgdb-pipe-*" -or -name "vg_logs_*" -or -name "valgrind.*" \
82 echo "See http://www.chromium.org/developers/how-tos/using-valgrind/dr-memory"
/external/pcre/dist2/
DRunGrepTest25 # valgrind settings when requested.
41 valgrind=
44 valgrind) valgrind="valgrind -q --leak-check=no --smc-check=all-non-file";;
52 if [ "$valgrind" = "" ] ; then
55 echo "Testing $pcre2grep_version using valgrind"
58 vjs="--suppressions=./testdata/valgrind-jit.supp"
104 $valgrind $pcre2grep $1 >>testtrygrep 2>&1
116 (cd $srcdir; $valgrind $vjs $pcre2grep PATTERN ./testdata/grepinput) >>testtrygrep
120 (cd $srcdir; $valgrind $vjs $pcre2grep '^PATTERN' ./testdata/grepinput) >>testtrygrep
124 (cd $srcdir; $valgrind $vjs $pcre2grep -in PATTERN ./testdata/grepinput) >>testtrygrep
[all …]
DRunTest27 # Other arguments can be one of the words "-valgrind", "-valgrind-log", or
33 # For backwards compatibility, -nojit, -valgrind, -valgrind-log, and -sim may
170 $valgrind $vjs ./pcre2test $1 >>testtry
181 $valgrind ./pcre2test -C ebcdic >/dev/null
206 valgrind=
276 valgrind|-valgrind) valgrind="valgrind --tool=memcheck -q --smc-check=all-non-file";;
277valgrind-log|-valgrind-log) valgrind="valgrind --tool=memcheck --num-callers=30 --leak-check=no --…
396 # When JIT is used with valgrind, we need to set up valgrind suppressions as
397 # otherwise there are a lot of false positive valgrind reports when the
405 if [ "$valgrind" != "" ] ; then
[all …]
/external/skqp/infra/bots/assets/valgrind/
Dcreate.py25 VALGRIND = 'valgrind-3.13.0' variable
26 TARBALL = '%s.tar.bz2' % VALGRIND
27 DOWNLOAD_URL = 'ftp://sourceware.org/pub/valgrind/%s' % TARBALL
28 TEMP_DIR = os.path.join(tempfile.gettempdir(), 'skia-%s' % VALGRIND)
42 if os.path.isdir(VALGRIND):
54 if os.path.isfile(os.path.join(INSTALL_DIR, 'bin', 'valgrind')):
56 with utils.chdir(os.path.join(TEMP_DIR, VALGRIND)):
63 with utils.chdir(os.path.join(TEMP_DIR, VALGRIND)):
65 shutil.copy(os.path.join(INSTALL_DIR, 'bin', 'valgrind'),
66 os.path.join(target_dir, 'bin', 'valgrind'))
[all …]
/external/skia/infra/bots/assets/valgrind/
Dcreate.py26 VALGRIND = 'valgrind-3.15.0' variable
27 TARBALL = '%s.tar.bz2' % VALGRIND
28 DOWNLOAD_URL = 'ftp://sourceware.org/pub/valgrind/%s' % TARBALL
29 TEMP_DIR = os.path.join(tempfile.gettempdir(), 'skia-%s' % VALGRIND)
43 if os.path.isdir(VALGRIND):
55 if os.path.isfile(os.path.join(INSTALL_DIR, 'bin', 'valgrind')):
57 with utils.chdir(os.path.join(TEMP_DIR, VALGRIND)):
64 with utils.chdir(os.path.join(TEMP_DIR, VALGRIND)):
66 shutil.copy(os.path.join(INSTALL_DIR, 'bin', 'valgrind'),
67 os.path.join(target_dir, 'bin', 'valgrind'))
[all …]
/external/python/cpython3/Modules/_decimal/tests/
Drunall-memorydebugger.sh5 # refleaks, release build and release build with valgrind.
9 # Requirements: valgrind
20 VALGRIND="valgrind --tool=memcheck --leak-resolution=high \
21 --suppressions=Misc/valgrind-python.supp"
59 # test_decimal: refleak, regular and Valgrind tests
97 ########### valgrind tests ###########
98 valgrind=$VALGRIND
100 # Valgrind has no support for 80 bit long double arithmetic.
101 ppro) valgrind= ;;
103 i386|i486|i586|i686) valgrind= ;;
[all …]
/external/libyuv/files/
D.gitignore62 /tools/valgrind
63 /tools/valgrind-libyuv/libyuv_tests.bat
64 /tools/valgrind-libyuv/libyuv_tests.py
65 /tools/valgrind-libyuv/libyuv_tests.sh
66 /tools/valgrind-libyuv/memcheck/OWNERS
67 /tools/valgrind-libyuv/memcheck/PRESUBMIT.py
68 /tools/valgrind-libyuv/memcheck/suppressions.txt
69 /tools/valgrind-libyuv/memcheck/suppressions_mac.txt
70 /tools/valgrind-libyuv/memcheck/suppressions_win32.txt
71 /tools/valgrind-libyuv/tsan/OWNERS
[all …]
/external/python/cpython3/Misc/
DREADME.valgrind1 This document describes some caveats about the use of Valgrind with
2 Python. Valgrind is used periodically by Python developers to try
5 If you want to enable valgrind support in Python, you will need to
6 configure Python --with-valgrind option or an older option
12 If you don't want to read about the details of using Valgrind, there
15 Misc/valgrind-python.supp. Second, you must do one of the following:
19 * Uncomment the lines in Misc/valgrind-python.supp that
22 If you want to use Valgrind more effectively and catch even more
26 from the big blocks. This means Valgrind can't detect
29 makes Python run much slower, especially when running under Valgrind.
[all …]
/external/python/cpython2/Misc/
DREADME.valgrind1 This document describes some caveats about the use of Valgrind with
2 Python. Valgrind is used periodically by Python developers to try
5 If you don't want to read about the details of using Valgrind, there
8 Misc/valgrind-python.supp. Second, you must do one of the following:
12 * Uncomment the lines in Misc/valgrind-python.supp that
15 If you want to use Valgrind more effectively and catch even more
19 from the big blocks. This means Valgrind can't detect
22 makes Python run much slower, especially when running under Valgrind.
23 You may need to run the tests in batches under Valgrind to keep
28 test_ctypes causes Valgrind 3.1.1 to fail (crash).
[all …]
/external/llvm/lib/Support/
DValgrind.cpp1 //===-- Valgrind.cpp - Implement Valgrind communication ---------*- C++ -*-===//
10 // Defines Valgrind communication methods, if HAVE_VALGRIND_VALGRIND_H is
11 // defined. If we have valgrind.h but valgrind isn't running, its macros are
16 #include "llvm/Support/Valgrind.h"
21 #include <valgrind/valgrind.h>
30 // Valgrind-provided macros.
/external/iptables/iptables/tests/shell/
Drun-tests.sh9 Usage: $(basename $0) [-v|--verbose] [-H|--host] [-V|--valgrind]
15 -V | --valgrind Enable leak checking via valgrind.
64 -V|--valgrind)
65 VALGRIND=y
99 # note: valgrind man page warns about --log-file with --trace-children, the
104 valgrind --log-file=$2/valgrind.log --trace-children=yes \
109 if grep -q 'no leaks are possible' $2/valgrind.log; then
110 rm $2/valgrind.log
112 mv $2/valgrind.log $2/valgrind_\$\$.log
122 if [ "$VALGRIND" == "y" ]; then
[all …]
/external/llvm-project/llvm/lib/Support/
DValgrind.cpp1 //===-- Valgrind.cpp - Implement Valgrind communication ---------*- C++ -*-===//
9 // Defines Valgrind communication methods, if HAVE_VALGRIND_VALGRIND_H is
10 // defined. If we have valgrind.h but valgrind isn't running, its macros are
15 #include "llvm/Support/Valgrind.h"
20 #include <valgrind/valgrind.h>
29 // Valgrind-provided macros.
/external/swiftshader/third_party/llvm-10.0/llvm/lib/Support/
DValgrind.cpp1 //===-- Valgrind.cpp - Implement Valgrind communication ---------*- C++ -*-===//
9 // Defines Valgrind communication methods, if HAVE_VALGRIND_VALGRIND_H is
10 // defined. If we have valgrind.h but valgrind isn't running, its macros are
15 #include "llvm/Support/Valgrind.h"
20 #include <valgrind/valgrind.h>
29 // Valgrind-provided macros.
/external/swiftshader/third_party/llvm-subzero/include/llvm/Support/
DValgrind.h1 //===- llvm/Support/Valgrind.h - Communication with Valgrind ----*- C++ -*-===//
10 // Methods for communicating with a valgrind instance this program is running
12 // valgrind headers installed and valgrind is controlling this process.
23 // True if Valgrind is controlling this process.
26 // Discard valgrind's translation of code in the range [Addr .. Addr + Len).
27 // Otherwise valgrind may continue to execute the old version of the code.
/external/llvm/include/llvm/Support/
DValgrind.h1 //===- llvm/Support/Valgrind.h - Communication with Valgrind ----*- C++ -*-===//
10 // Methods for communicating with a valgrind instance this program is running
12 // valgrind headers installed and valgrind is controlling this process.
23 // True if Valgrind is controlling this process.
26 // Discard valgrind's translation of code in the range [Addr .. Addr + Len).
27 // Otherwise valgrind may continue to execute the old version of the code.
/external/swiftshader/third_party/llvm-10.0/llvm/include/llvm/Support/
DValgrind.h1 //===- llvm/Support/Valgrind.h - Communication with Valgrind ----*- C++ -*-===//
9 // Methods for communicating with a valgrind instance this program is running
11 // valgrind headers installed and valgrind is controlling this process.
22 // True if Valgrind is controlling this process.
25 // Discard valgrind's translation of code in the range [Addr .. Addr + Len).
26 // Otherwise valgrind may continue to execute the old version of the code.
/external/llvm-project/llvm/include/llvm/Support/
DValgrind.h1 //===- llvm/Support/Valgrind.h - Communication with Valgrind ----*- C++ -*-===//
9 // Methods for communicating with a valgrind instance this program is running
11 // valgrind headers installed and valgrind is controlling this process.
22 // True if Valgrind is controlling this process.
25 // Discard valgrind's translation of code in the range [Addr .. Addr + Len).
26 // Otherwise valgrind may continue to execute the old version of the code.
/external/flac/test/
Dtest_replaygain.sh38 …echo "valgrind --leak-check=yes --show-reachable=yes --num-callers=50 flac $*" >>test_replaygain.v…
39valgrind --leak-check=yes --show-reachable=yes --num-callers=50 --log-fd=4 flac --no-error-on-comp…
48 …echo "valgrind --leak-check=yes --show-reachable=yes --num-callers=50 metaflac $*" >>test_replayga…
49valgrind --leak-check=yes --show-reachable=yes --num-callers=50 --log-fd=4 metaflac $* 4>>test_rep…
61 …echo "valgrind --leak-check=yes --show-reachable=yes --num-callers=50 metaflac $*" >>test_replayga…
62valgrind --leak-check=yes --show-reachable=yes --num-callers=50 --log-fd=4 metaflac $* 2>/dev/null…
/external/harfbuzz_ng/test/fuzzing/
Drun-shape-fuzzer-tests.py77 valgrind = None variable
79 valgrind = which ('valgrind') variable
80 if valgrind is None:
81 print ("""Valgrind requested but not found.""")
84 print ("""Valgrind support is currently autotools only and needs libtool but not found.""")
91 if valgrind:
92 …text, returncode = cmd (libtool.split(' ') + ['--mode=execute', valgrind + ' --leak-check=full --e…
98 if (not valgrind or returncode) and text.strip ():
/external/libchrome/base/third_party/valgrind/
DREADME.chromium1 Name: valgrind
2 URL: http://valgrind.org
6 current process is running under Valgrind and tell Memcheck tool about custom
9 These header files were taken from Valgrind source code
10 (svn://svn.valgrind.org/valgrind/trunk@11504, dated 21 Jan 2011). The files are

12345678910>>...33