wireshark

Commit Graph

Author	SHA1	Message	Date
Evan Huus	aafe8b18e9	Remove the wmem slab. It was an optimization mimicking the emem slab (removed in r48218) which did nothing particularly useful. Also lets us remove another debugging environment variable. svn path=/trunk/; revision=48219	2013-03-09 20:16:33 +00:00
Evan Huus	5071e8b627	Add an option for bypassing the wmem slab similar to the one for bypassing the emem slab, to aid in debugging with valgrind. svn path=/trunk/; revision=47656	2013-02-14 16:07:25 +00:00
Gerald Combs	3c66ac4b83	Forward-port r47305 from trunk-1.8: ------------------------------------------------------------------------ r47305 \| gerald \| 2013-01-26 12:12:52 -0800 (Sat, 26 Jan 2013) \| 6 lines Changed paths: M /trunk-1.8/tools/fuzz-test.sh Instead of setting resource limits on the fuzz-test.sh process itself, set limits on the TShark subprocess. This should hopefully take care of the strange fuzz failures we've seen lately. Reduce the maximum CPU time to 5 minutes while we're at it. ------------------------------------------------------------------------ svn path=/trunk/; revision=47307	2013-01-26 20:36:57 +00:00
Gerald Combs	aafa77c6f4	Try to show what condition triggered a failure. svn path=/trunk/; revision=47079	2013-01-14 20:17:20 +00:00
Evan Huus	5eacf33f1f	Update wmem documentation for the new allocator. Use the strict allocator when fuzzing (at least until the fuzz-bot starts running everything under valgrind). svn path=/trunk/; revision=46829	2012-12-28 17:09:07 +00:00
Gerald Combs	739c90f0ad	Move a lot of common fuzz-test and randpkt-test code to its own file (test-common.sh). Add build information to the error output as suggested in http://www.wireshark.org/lists/wireshark-dev/201212/msg00037.html svn path=/trunk/; revision=46446	2012-12-07 17:57:09 +00:00

6 Commits