summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthew Horsfall (alh) <wolfsage@gmail.com>2014-05-28 13:53:19 -0400
committerMatthew Horsfall (alh) <wolfsage@gmail.com>2014-05-28 13:53:19 -0400
commit037ab3f1c4cd56bf6a5c16524d40f3636295fc32 (patch)
tree10e03f998f37cbe74f18fc21b28d42f8b20cf933
parent60f7fc1ea42054e92f34b4ce9d608efd14357392 (diff)
downloadperl-037ab3f1c4cd56bf6a5c16524d40f3636295fc32.tar.gz
[perl #121431] - Document test.valgrind in perlhacktips.pod
-rw-r--r--pod/perlhacktips.pod18
1 files changed, 17 insertions, 1 deletions
diff --git a/pod/perlhacktips.pod b/pod/perlhacktips.pod
index 2f19c04b83..ccc38ad89f 100644
--- a/pod/perlhacktips.pod
+++ b/pod/perlhacktips.pod
@@ -1073,7 +1073,23 @@ heap memory accesses. As of version 3.3.0, Valgrind only supports Linux
on x86, x86-64 and PowerPC and Darwin (OS X) on x86 and x86-64). The
special "test.valgrind" target can be used to run the tests under
valgrind. Found errors and memory leaks are logged in files named
-F<testfile.valgrind>.
+F<testfile.valgrind> and by default output is displayed inline.
+
+Example usage:
+
+ make test.valgrind
+
+Since valgrind adds significant overhead, tests will take much longer to
+run. The valgrind tests support being run in parallel to help with this:
+
+ TEST_JOBS=9 make test.valgrind
+
+Note that the above two invocations will be very verbose as reachable
+memory and leak-checking is enabled by default. If you want to just see
+pure errors, try:
+
+ VG_OPTS='-q --leak-check=no --show-reachable=no' TEST_JOBS=9 \
+ make test.valgrind
Valgrind also provides a cachegrind tool, invoked on perl as: