Lines Matching refs:fuzz

5 `tests/fuzz/fd-fuzz.cpp` exercises the FD responder implementation. It can run
8 Each fuzz corpus input is split into two parts. The first 1024 bytes is a
13 The remainder of the fuzz input is taken as an stream of `length:data` PLDM
18 From the top level libpldm directory, run `./tests/fuzz/fuzz-build.py`. That
19 will produce several build variants required for different fuzz engines/stages.
30 …e honggfuzz -i corpusdir --linux_perf_branch --dict tests/fuzz/fd.dict  -- ./bhf/tests/fuzz/fd-fuzz
44 totally fresh start, copy in `tests/fuzz/fd-fuzz-input1.dat`, a sample
52 afl-fuzz -i fuzzrun/hf11/ -o fuzzrun/out12single ./bfuzz/tests/fuzz/fd-fuzz
61 …fuzz/fd-fuzz -i workdir/out5/m_fd-fuzz/queue -o workdir/out6 -c bcmplog/tests/fuzz/fd-fuzz -s bfuz…
64 Kill it with `aflr kill fuzz`.
73 `tests/fuzz/fuzz-coverage.py`.
85 ./tests/fuzz/fuzz-coverage.py fuzzrun/corpus bnoopt/tests/fuzz/fd-fuzz . bnoopt/ coverage-output
90 When the fuzz run encounters a crash, the testcase can be run against the built
94 env TRACEFWFD=1 ./bnoopt/tests/fuzz/fd-fuzz < crashing.bin