[Wireshark-bugs] [Bug 14341] Buildbot crash output: fuzz-2018-01-13-1912.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14341

--- Comment #2 from Guy Harris  ---
(In reply to Guy Harris from comment #1)
> It looks as if it might have timed out:
> 
> ./tools/fuzz-test.sh: line 204: 21195 CPU time limit exceeded (core dumped)
> "$RUNNER" $COMMON_ARGS $ARGS $TMP_DIR/$TMP_FILE > /dev/null 2>>
> $TMP_DIR/$ERR_FILE.$SUBSHELL_PID

Running on my 2.8 GHz Intel Core i7 MacBook Pro (Retina, 15 inch, Mid 2015, so
Crystalwell):

$ time ./tshark -n -V -r ~/Downloads/fuzz-2018-01-13-1912.pcap >/dev/null

real0m53.630s
user0m52.374s
sys 0m0.842s

so it eventually finishes - it doesn't appear to be stuck in an infinite loop.

That fits within the 600 seconds that tools/test-common.sh specifies - and the
1800 seconds that would be used with Valgrind - but maybe it's too small for
the test machine, or maybe there's something that causes it to loop infinitely
on the test machine.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14341] Buildbot crash output: fuzz-2018-01-13-1912.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14341

--- Comment #1 from Guy Harris  ---
It looks as if it might have timed out:

./tools/fuzz-test.sh: line 204: 21195 CPU time limit exceeded (core dumped)
"$RUNNER" $COMMON_ARGS $ARGS $TMP_DIR/$TMP_FILE > /dev/null 2>>
$TMP_DIR/$ERR_FILE.$SUBSHELL_PID

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe