Add some fuzzers to test other data structures. (#1870)

Start using a dictionary for fuzzing (see:
https://llvm.org/docs/LibFuzzer.html#dictionaries).
Remove some dead code.
Fuzzing with debug enabled is not usually a great idea (from performance
POV). Keep the code since it might be useful while debugging.

1 files changed, 1 insertions, 1 deletions

diff --git a/tests/do.sh.in b/tests/do.sh.in
index e8d6b60e5..62823b2bd 100755
--- a/tests/do.sh.in
+++ b/tests/do.sh.in
@@ -56,7 +56,7 @@ fuzzy_testing() {
 	cp ../example/risky_domains.txt .
 	cp ../example/ja3_fingerprints.csv .
 	cp ../example/sha1_fingerprints.csv .
-	../fuzz/fuzz_ndpi_reader -max_total_time="${MAX_TOTAL_TIME:-592}" -print_pcs=1 -workers="${FUZZY_WORKERS:-0}" -jobs="${FUZZY_JOBS:-0}" pcap/
+	../fuzz/fuzz_ndpi_reader -dict=..fuzz/dictionary.dict -max_total_time="${MAX_TOTAL_TIME:-592}" -print_pcs=1 -workers="${FUZZY_WORKERS:-0}" -jobs="${FUZZY_JOBS:-0}" pcap/
 	rm -f protos.txt categories.txt risky_domains.txt ja3_fingerprints.csv sha1_fingerprints.csv
     fi
 }