From 3bc24f2d989b6297d9d1cf56ffa5d893936cfae9 Mon Sep 17 00:00:00 2001
From: Gerald Combs <gerald@wireshark.org>
Date: Wed, 7 Jul 2010 16:55:42 +0000
Subject: Try limiting our stack size.

svn path=/trunk/; revision=33466
---
 tools/fuzz-test.sh | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

(limited to 'tools')

diff --git a/tools/fuzz-test.sh b/tools/fuzz-test.sh
index 13970d39a2..117e715c1d 100755
--- a/tools/fuzz-test.sh
+++ b/tools/fuzz-test.sh
@@ -32,10 +32,17 @@ MAX_PASSES=0
 TWO_PASS=
 
 # These may be set to your liking
-# Stop the child process, if it's running longer than x seconds
+# Stop the child process if it's running longer than x seconds
 MAX_CPU_TIME=900
-# Stop the child process, if it's using more than y * 1024 bytes
+# Stop the child process if it's using more than y * 1024 bytes
 MAX_VMEM=500000
+# Stop the child process if its stack is larger than than z * 1024 bytes
+# Windows XP:   2033
+# Windows 7:    2034
+# OS X 10.6:    8192
+# Linux 2.6.24: 8192
+# Solaris 10:   8192
+MAX_STACK=2033
 # Insert z times an error into the capture file (0.02 seems to be a good value to find errors)
 ERR_PROB=0.02
 # Trigger an abort if a dissector finds a bug.
@@ -69,7 +76,7 @@ fi
 
 # set some limits to the child processes, e.g. stop it if it's running longer then MAX_CPU_TIME seconds
 # (ulimit is not supported well on cygwin and probably other platforms, e.g. cygwin shows some warnings)
-ulimit -S -t $MAX_CPU_TIME -v $MAX_VMEM
+ulimit -S -t $MAX_CPU_TIME -v $MAX_VMEM -s $MAX_STACK
 ulimit -c unlimited
 
 ### usually you won't have to change anything below this line ###
-- 
cgit v1.2.3