Add a valgrind suppressions file set to suppress the zlib error which otherwise

pops up immediately on the fuzzbot. Hopefully there won't be too many more of
these.

svn path=/trunk/; revision=51434
This commit is contained in:
Evan Huus 2013-08-20 03:21:06 +00:00
parent f0a66b2e3e
commit 1a884bf191
2 changed files with 17 additions and 1 deletions

View File

@ -102,4 +102,4 @@ else
LIBTOOL=""
fi
$LIBTOOL valgrind $TOOL $VERBOSE $LEAK_CHECK $REACHABLE $TRACK_ORIGINS $COMMAND $COMMAND_ARGS $PCAP $COMMAND_ARGS2 > /dev/null
$LIBTOOL valgrind --suppressions=`dirname $0`/vg-suppressions $TOOL $VERBOSE $LEAK_CHECK $REACHABLE $TRACK_ORIGINS $COMMAND $COMMAND_ARGS $PCAP $COMMAND_ARGS2 > /dev/null

16
tools/vg-suppressions Normal file
View File

@ -0,0 +1,16 @@
# This file lists suppressions to hide valgrind errors in libraries we don't
# control. Be careful adding to it, since overly-broad suppressions may hide
# real errors in Wireshark!
#
# This is primarily targeted towards the set of libraries on the fuzz-bot (which
# runs a valgrind step) but other entries are welcome as long as they are
# sufficiently commented.
# Zlib 1.2.3.4 on the buildbot hits an uninitialized jump on the first call to
# inflateReset2. According to the Zlib changelog this was fixed in 1.2.3.7.
{
libz/inflateReset2/jump
Memcheck:Cond
fun:inflateReset2
fun:inflateInit2_
}