Export MALLOC_CHECK_=3 when fuzz testing in case we're on a glibc-based system:
authormorriss <morriss@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 21 Apr 2010 00:53:24 +0000 (00:53 +0000)
committermorriss <morriss@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 21 Apr 2010 00:53:24 +0000 (00:53 +0000)
this value will cause glibc to do some memory allocation checking for us and
abort if it finds a problem.

(If we're not on a glibc-based system this will have no effect but should also
do no harm.)

(I think the buildbot already runs with this set but it's better for all of us
to have it set, too.)

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@32528 f5534014-38df-0310-8fa8-9805f1628bb7

tools/fuzz-test.sh
tools/test-fuzzed-cap.sh

index fd4baa74e042057dc47d1a779efa72fc5231f96b..c21fc40c1cfdf8e6bf8e542c8021e957a2f891cf 100755 (executable)
@@ -165,8 +165,9 @@ while [ $PASS -lt $MAX_PASSES -o $MAX_PASSES -lt 1 ] ; do
         fi
     fi
 
-    export WIRESHARK_DEBUG_SCRUB_MEMORY=1
-    export WIRESHARK_DEBUG_SE_USE_CANARY=1
+    export WIRESHARK_DEBUG_SCRUB_MEMORY=
+    export WIRESHARK_DEBUG_SE_USE_CANARY=
+    export MALLOC_CHECK_=3
     "$TSHARK" $TSHARK_ARGS $TMP_DIR/$TMP_FILE \
         > /dev/null 2> $TMP_DIR/$ERR_FILE
     RETVAL=$?
index 3abb874b795701262b03b2f4192f84c358abbac4..d43704be00c57ff6f08a06dcbbc875a69f0cc3d0 100755 (executable)
@@ -26,7 +26,8 @@ ulimit -S -t $MAX_CPU_TIME -v $MAX_VMEM
 # Allow core files to be generated
 ulimit -c unlimited
 
-export WIRESHARK_DEBUG_SCRUB_MEMORY=1
-export WIRESHARK_DEBUG_SE_USE_CANARY=1
+export WIRESHARK_DEBUG_SCRUB_MEMORY=
+export WIRESHARK_DEBUG_SE_USE_CANARY=
+export MALLOC_CHECK_=3
 
 ./tshark -nVxr $1 > /dev/null