harfbuzz

History

Khaled Hosny 0af3d176a6 [sbix] Fix memory leak in early return Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11210		2018-10-30 17:05:28 +02:00
..
fonts	[sbix] Fix memory leak in early return	2018-10-30 17:05:28 +02:00
CMakeLists.txt	Remove remains of get-codepoint-fuzzer	2018-10-11 17:31:29 -04:00
Makefile.am	Add all the fonts found by fuzzers to the repo (#1258 )	2018-10-17 01:42:04 +03:30
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	Minor, tweak spaces on hb-shape-fuzzer.cc	2018-10-19 09:39:36 +03:30
hb-subset-fuzzer.cc	[fuzzing] Fold get-codepoints-fuzzer into subset-fuzzer	2018-10-11 17:08:12 -04:00
main.cc	Minor	2018-10-11 15:42:54 -04:00
run-shape-fuzzer-tests.py	[fuzzing] Make test runners less verbose	2018-10-29 22:53:16 -07: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