As discussed in https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8728#c4 :

Running tshark with a read filter ("-R") and without building the full tree
("-V") causes it to run into some more bugs (usually loops adding more than
100000 items to the tree).  Add some (commented out for now) code to do
this...

svn path=/trunk/; revision=49643

tools/fuzz-test.sh

@@ -60,6 +60,13 @@ else
     # r Read packet data from the following infile
     RUNNER="$TSHARK"
     declare -a RUNNER_ARGS=("${CONFIG_PROFILE}${TWO_PASS}-nVxr" "${CONFIG_PROFILE}${TWO_PASS}-nr")
+    # Running with a read filter but without generating the tree exposes some "More than 100000 items
+    # in tree" bugs (which currently need WIRESHARK_ABORT_ON_DISSECTOR_BUG to be noticed--maybe that
+    # error should have its own environment variable?).
+    # Leave this commented out for now until someone has time to run it through the menagerie once
+    # or twice (so we don't get buried in bugs)...
+    #declare -a RUNNER_ARGS=("${CONFIG_PROFILE}${TWO_PASS}-nVxr" "${CONFIG_PROFILE}${TWO_PASS}-nr" "-Rframe ${CONFIG_PROFILE}${TWO_PASS}-nr")
+    #export WIRESHARK_ABORT_ON_DISSECTOR_BUG=
 fi
 
 

tools/test-captures.sh

@@ -55,6 +55,17 @@ do
 		if $BIN_DIR/tshark -nr $file > /dev/null
 		then
 			echo "OK"
+			# We may not be ready to looking for all these bugs yet...
+			#echo -n " - without tree but with a read filter... "
+			#export WIRESHARK_ABORT_ON_DISSECTOR_BUG=
+			#if $BIN_DIR/tshark -Rframe -nr $file > /dev/null
+			#then
+			#	echo "OK"
+			#else
+			#	echo "Failed"
+			#	exit 1
+			#fi
+			#unset WIRESHARK_ABORT_ON_DISSECTOR_BUG
 		else
 			echo "Failed"
 			exit 1