so far will take a while and in the meantime looking for dissector
assertions is keeping us from finding more serious bugs.
svn path=/trunk/; revision=29395
1. If enabled: the variable must be exported to the env to take effect;
2. Upon reflection: disable this feature:
tshark has been changed to output WARNING messages to stderr as a
default; This means that DISSECTOR_BUGs and failed DISSECTOR_ASSERTs
which cause WARNING log level messages will thus be output to stderr and
thus will be detected by the fuzz-test.
svn path=/trunk/; revision=29330
I noticed that when you run fuzz testing from both a root account and
a user account you can run into problems because the user account tries
to use and delete temp files created by the root account and fails. This
patch uses the same scheme as used for fuzz error files for naming the
tampered file and for the error file to prevent filename/permission
collisions between temp files from different runs.
svn path=/trunk/; revision=17145
Limit the amount of VM the process can use (default 500 MB). If we
can't save a capture in libpcap format, try again with the encapsulation
type set to "ether".
svn path=/trunk/; revision=14156
"./tools/fuzz-test.sh /path/to/capture/files/*" will iterate over the
specified capture files, using editcap to introduce errors and tethereal
to check for bugs. It will do this until tethereal exits abnormally or
a dissector bug is encountered.
svn path=/trunk/; revision=14073