Lines Matching refs:fuzzer

15 Install `clang`, which [ships with `libfuzzer`](http://llvm.org/docs/LibFuzzer.html#fuzzer-usage)
23 `/usr/lib/llvm-7/lib/clang/7.0.1/lib/linux/libclang_rt.fuzzer-x86_64.a`.
26             --with-fuzzer-lib=$PATH_TO_LIBFUZZER \
29             -fsanitize=fuzzer-no-link \
59 a `--with-fuzzer-include` option, which should be the parent directory of the
60 prebuilt fuzzer library. This is represented as `$PATH_TO_LIBFUZZER_DIR` below.
63             --with-fuzzer-include=$PATH_TO_LIBFUZZER_DIR \
64             --with-fuzzer-lib=$PATH_TO_LIBFUZZER \
67             -fsanitize=fuzzer-no-link \
100 If a fuzzer generates a reproducible error, you can reproduce the problem using
101 the fuzz/*-test binaries and the file generated by the fuzzer. They binaries
105 be useful to show you when the problem happens. For the client and server fuzzer
113 To do all the tests of a specific fuzzer such as asn1 you can run
130 The client and server fuzzer normally generate random numbers as part of the TLS
137 server fuzzer will use predictable numbers instead of the random numbers. This
142 numbers that were generated. For instance the client fuzzer will always generate
162 - A default config, plus options needed to generate the fuzzer.
170 When you have gathered corpus data from more than one fuzzer run