harfbuzz

History

Behdad Esfahbod b7384c89e2 [fuzzing] Run valgrind with --leak-check=full		2019-04-15 16:53:10 -04:00
..
fonts	Use class templates for Null objects	2019-03-26 16:23:40 -07:00
CMakeLists.txt	Remove remains of get-codepoint-fuzzer	2018-10-11 17:31:29 -04:00
Makefile.am	[fuzzing] Remove limited-edition build of libraries	2018-11-12 13:21:14 -05:00
README	Move all references of old url to the new address (#622 )	2017-11-20 14:49:22 -05:00
hb-fuzzer.hh	[fuzzer] Separate main() into a new file	2016-12-20 20:50:38 -06:00
hb-shape-fuzzer.cc	[fuzzing] Take whatever text we can	2018-11-07 19:12:27 -05:00
hb-subset-fuzzer.cc	[subset] Update the subset fuzzer to determine which options to use based on data in the fuzzing test case.	2019-01-30 15:23:19 -08:00
main.cc	Minor	2018-10-11 15:42:54 -04:00
run-shape-fuzzer-tests.py	[fuzzing] Run valgrind with --leak-check=full	2019-04-15 16:53:10 -04:00
run-subset-fuzzer-tests.py	[fuzzing] Make test runners less verbose	2018-10-29 22:53:16 -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