11d583a9ea
Glyph insertion is an expensive operation and we like to have it limited based on buffer's input size which is handled by buffer's max_ops. clusterfuzz-testcase-minimized-harfbuzz_fuzzer-5754958982021120: Before the change: 0.67s user 0.00s system 99% cpu 0.674 total After the change: 0.02s user 0.00s system 98% cpu 0.024 total Which takes much longer on valgrind and tsan bots. |
||
---|---|---|
.. | ||
fonts | ||
sets | ||
hb-draw-fuzzer.cc | ||
hb-fuzzer.hh | ||
hb-set-fuzzer.cc | ||
hb-shape-fuzzer.cc | ||
hb-subset-fuzzer.cc | ||
main.cc | ||
Makefile.am | ||
meson.build | ||
README | ||
run-draw-fuzzer-tests.py | ||
run-shape-fuzzer-tests.py | ||
run-subset-fuzzer-tests.py |
In order to build the fuzzer one needs to build HarfBuzz and harfbuzz/test/fuzzing/hb-fuzzer.cc with: - Using the most recent Clang - With -fsanitize=address (or =undefined, or a combination) - With -fsanitize-coverage=edge[,8bit-counters,trace-cmp] - With various defines that limit worst case exponential behavior. See FUZZING_CPPFLAGS in harfbuzz/src/Makefile.am for the list. - link against libFuzzer To run the fuzzer one needs to first obtain a test corpus as a directory containing interesting fonts. A good starting point is inside harfbuzz/test/shaping/fonts/fonts/. Then, run the fuzzer like this: ./hb-fuzzer -max_len=2048 CORPUS_DIR Where max_len specifies the maximal length of font files to handle. The smaller the faster. For more details consult the following locations: - http://llvm.org/docs/LibFuzzer.html or - https://github.com/google/libfuzzer-bot/tree/master/harfbuzz - https://github.com/harfbuzz/harfbuzz/issues/139