harfbuzz/test/fuzzing
Michiharu Ariza 8341c0b304 add test case file 2019-06-27 08:43:31 -07:00
..
fonts add test case file 2019-06-27 08:43:31 -07:00
CMakeLists.txt Remove remains of get-codepoint-fuzzer 2018-10-11 17:31:29 -04:00
Makefile.am [valgrind] Use libtool and support run-subset-fuzzer-tests (#1668) 2019-04-28 11:54:07 -07: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 test: Use nullptr in C++ code. (#1744) 2019-06-03 12:30:25 +04:30
hb-subset-fuzzer.cc test: Use nullptr in C++ code. (#1744) 2019-06-03 12:30:25 +04:30
main.cc [test] minor, fix -Weverything bot 2019-05-11 18:48:41 -04:00
run-shape-fuzzer-tests.py [valgrind] Use libtool and support run-subset-fuzzer-tests (#1668) 2019-04-28 11:54:07 -07:00
run-subset-fuzzer-tests.py [valgrind] Use libtool and support run-subset-fuzzer-tests (#1668) 2019-04-28 11:54:07 -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