harfbuzz

History

Ebrahim Byagowi 4e3cf91af2 [cmake] Run rest of the tests on Windows (#668 )		2018-01-01 11:17:51 +03:30
..
CMakeLists.txt	[cmake] Run rest of the tests on Windows (#668 )	2018-01-01 11:17:51 +03:30
Makefile.am	[cmake] Run rest of the tests on Windows (#668 )	2018-01-01 11:17:51 +03:30
README	Move all references of old url to the new address (#622 )	2017-11-20 14:49:22 -05:00
hb-fuzzer.cc	Ouch, finish previous change	2016-12-20 20:52:50 -06:00
hb-fuzzer.hh	[fuzzer] Separate main() into a new file	2016-12-20 20:50:38 -06:00
main.cc	[fuzzer] Separate main() into a new file	2016-12-20 20:50:38 -06:00
run-fuzzer-tests.py	[cmake] Run rest of the tests on Windows (#668 )	2018-01-01 11:17:51 +03:30

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