init.sh: enable MALLOC_PERTURB_

* tests/init.sh: Enable glibc's malloc-perturbing option.

diff --git a/ChangeLog b/ChangeLog
index 63d40c327c3f53eed020aebcd9975de3661db9b4..f2efae51cd849d92334e47aa7c89e5d91eb4de38 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -9,6 +9,9 @@
 
 2010-05-09  Jim Meyering  <meyering@redhat.com>
 
+       init.sh: enable MALLOC_PERTURB_
+       * tests/init.sh: Enable glibc's malloc-perturbing option.
+
        maint.mk: improve sc_cross_check_PATH_usage_in_tests
        With my recent change in init.sh from the two-line form:
            -#   : ${srcdir=.}

diff --git a/tests/init.sh b/tests/init.sh
index 777273697011883491a2a8111b3d6cb18c9eb0e5..1c0b4b4f1146d3b4b3bbb56cb898fc20f5c580e0 100644 (file)
--- a/tests/init.sh
+++ b/tests/init.sh
@@ -94,6 +94,13 @@ fi
 
 test -n "$EXEEXT" && shopt -s expand_aliases
 
+# Enable glibc's malloc-perturbing option.
+# This is cheap and useful for exposing code that depends on the fact that
+# malloc-related functions often return memory that is mostly zeroed.
+# If you have the time and cycles, use valgrind to do an even better job.
+${MALLOC_PERTURB_=87}
+export MALLOC_PERTURB_
+
 # We use a trap below for cleanup.  This requires us to go through
 # hoops to get the right exit status transported through the handler.
 # So use `Exit STATUS' instead of `exit STATUS' inside of the tests.