search for: execs_per_sec

Displaying 3 results from an estimated 3 matches for "execs_per_sec".

2016 Sep 21
2
-sanitizer-coverage-prune-blocks=true and LibFuzzer
...0000000 DONE cov: 444 bits: 1675 indir: 12 units: 501 exec/s: 277777 > #10000000 DONE cov: 401 bits: 1443 indir: 12 units: 341 exec/s: 263157 > > I've also tried building with trace-pc-guard (the new thing) and results are similar. > name cov bits execs execs_per_sec units actual_cov actual_bits > asan-8bit-nopru 401 1443 19790806 324439 340 401 1441 > asan-8bit-prune 256 897 26528866 434899 485 447 1651 > asan-edge-nopru 447 0 35589496 583434 137 447 719 > asan-edge-p...
2016 Sep 21
2
-sanitizer-coverage-prune-blocks=true and LibFuzzer
...NE cov: 444 bits: 1675 indir: 12 units: 501 exec/s: 277777 >> #10000000 DONE cov: 401 bits: 1443 indir: 12 units: 341 exec/s: 263157 >> >> I've also tried building with trace-pc-guard (the new thing) and results are similar. >> name cov bits execs execs_per_sec units actual_cov actual_bits >> asan-8bit-nopru 401 1443 19790806 324439 340 401 1441 >> asan-8bit-prune 256 897 26528866 434899 485 447 1651 >> asan-edge-nopru 447 0 35589496 583434 137 447 719 >...
2016 Sep 21
3
-sanitizer-coverage-prune-blocks=true and LibFuzzer
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