summaryrefslogtreecommitdiff
path: root/tools/fuzz-test.sh
diff options
context:
space:
mode:
authorEvan Huus <eapache@gmail.com>2012-08-12 14:14:08 +0000
committerEvan Huus <eapache@gmail.com>2012-08-12 14:14:08 +0000
commit69cd2847878dd82b84a50ebd7c7ffd76755bf2aa (patch)
tree44083dd1a16c3e745b0afe75682a9c597ae6f675 /tools/fuzz-test.sh
parent645d61c2e77e250ffb226af53ffd60dae5d6d134 (diff)
downloadwireshark-69cd2847878dd82b84a50ebd7c7ffd76755bf2aa.tar.gz
Catch more types of valgrind errors in the fuzz-tester.
These happen when, eg, a program runs out of memory under valgrind or other more fatal errors (that may sometimes be valgrind bugs instead). svn path=/trunk/; revision=44451
Diffstat (limited to 'tools/fuzz-test.sh')
-rwxr-xr-xtools/fuzz-test.sh3
1 files changed, 3 insertions, 0 deletions
diff --git a/tools/fuzz-test.sh b/tools/fuzz-test.sh
index 20105cb091..75135abe73 100755
--- a/tools/fuzz-test.sh
+++ b/tools/fuzz-test.sh
@@ -253,6 +253,9 @@ while [ \( $PASS -lt $MAX_PASSES -o $MAX_PASSES -lt 1 \) -a $DONE -ne 1 ] ; do
if [ $VALGRIND -eq 1 ]; then
VG_ERR_CNT="`grep "ERROR SUMMARY:" $TMP_DIR/$ERR_FILE | cut -f4 -d' '`"
+ if grep -q "Valgrind cannot continue" $TMP_DIR/$ERR_FILE; then
+ VG_ERR_CNT=-1
+ fi
fi
if [ \( $RETVAL -ne 0 -o $DISSECTOR_BUG -ne 0 -o $VG_ERR_CNT -ne 0 \) \