harfbuzz/test/fuzzing
Garret Rieger 5ca353a2d0 [subset] fix heap buffer overflow found by fuzzer. 2021-02-16 12:43:02 -07:00
..
fonts [subset] fix heap buffer overflow found by fuzzer. 2021-02-16 12:43:02 -07:00
sets [fuzz] minor, move two fuzzer cases to their correct place 2020-02-12 19:17:18 +03:30
Makefile.am Revert "Remove autotools build support" 2020-08-11 23:51:59 +04:30
README Move all references of old url to the new address (#622) 2017-11-20 14:49:22 -05:00
hb-draw-fuzzer.cc [fuzzer] minor 2020-08-12 02:40:55 +04:30
hb-fuzzer.hh [fuzzer] minor 2020-08-12 02:40:55 +04:30
hb-set-fuzzer.cc [set fuzzer] limit the total number of set members in a fuzzing input. 2021-01-26 10:22:07 -08:00
hb-shape-fuzzer.cc [fuzzer] minor 2020-08-12 02:40:55 +04:30
hb-subset-fuzzer.cc [fuzzer] minor 2020-08-12 02:40:55 +04:30
main.cc [fuzz] minor don't abort main.cc when the file was empty or not found 2020-02-26 16:15:17 +03:30
meson.build [test] Remove timeout from test runners 2020-10-15 00:49:02 -07:00
run-draw-fuzzer-tests.py [test] Remove timeout from test runners 2020-10-15 00:49:02 -07:00
run-shape-fuzzer-tests.py [test] Remove timeout from test runners 2020-10-15 00:49:02 -07:00
run-subset-fuzzer-tests.py [test] Remove timeout from test runners 2020-10-15 00:49:02 -07:00

README

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