search for: fuzzer_testing_seconds

...ting! > > (btw, I'd prefer libfuzzer at googlegroups.com <mailto:libfuzzer at googlegroups.com> for such discussions, please start new topics there) You mean a LLVM library has a separate mailing-list? Why? — Mehdi > > I can reproduce this too, but if i either increase FUZZER_TESTING_SECONDS to 600 or change seed=1 to seed=2 the problem is gone. > Looks like one of the binaries got simply unlucky with a particular seed. > You can observe it like this: > for S in 1 2 3 4 5 6; do ./target-asan-8bit-prune-build/fuzzer -seed=$S -runs=10000000 2>&1 | grep DONE & done...

...about the development/debug/evolution/usability of http://llvm.org/svn/llvm-project/llvm/trunk/lib/Fuzzer/ <http://llvm.org/svn/llvm-project/llvm/trunk/lib/Fuzzer/> — Mehid > > > — > Mehdi > > >> >> I can reproduce this too, but if i either increase FUZZER_TESTING_SECONDS to 600 or change seed=1 to seed=2 the problem is gone. >> Looks like one of the binaries got simply unlucky with a particular seed. >> You can observe it like this: >> for S in 1 2 3 4 5 6; do ./target-asan-8bit-prune-build/fuzzer -seed=$S -runs=10000000 2>&1 | grep DONE...

Hello, Is this reproducible? > Fuzzing is a probabilistic business and one or even two runs don't prove > much. > I've reproduced the behavior on two different machines. Attached is a script to do so. To use the script, - create an empty folder and copy both prune-blocks.sh and ff-http-parser.sh in there - ensure clang and clang++ are in your $PATH - cd /path/to/prune-blocks.sh