Fuzz: Reduce the Valgrind packet limit to 10,000.
Limit Valgrind to the first 10,000 packets in each file. Change-Id: I27be212ddb437c643ffb413bb9d1c809dbe98a55 Reviewed-on: https://code.wireshark.org/review/29210 Petri-Dish: Gerald Combs <gerald@wireshark.org> Tested-by: Petri Dish Buildbot Reviewed-by: Gerald Combs <gerald@wireshark.org>
This commit is contained in:
parent
4b3745e6ef
commit
6ee559efd1
|
@ -82,10 +82,10 @@ if [ $VALGRIND -eq 1 ]; then
|
|||
# (1.5x time is too small for a few large captures in the menagerie)
|
||||
MAX_CPU_TIME=$(( 3 * MAX_CPU_TIME ))
|
||||
MAX_VMEM=$(( 3 * MAX_VMEM / 2 ))
|
||||
# Valgrind is slow. Trim captures to the first 100k packets so that
|
||||
# Valgrind is slow. Trim captures to the first 10k packets so that
|
||||
# we don't time out.
|
||||
KEEP=-r
|
||||
PACKET_RANGE=1-100000
|
||||
PACKET_RANGE=1-10000
|
||||
else
|
||||
# Not using valgrind, use regular tshark.
|
||||
# TShark arguments (you won't have to change these)
|
||||
|
|
Loading…
Reference in New Issue