harfbuzz/test/fuzzing
Ebrahim Byagowi 4146c00caa
[test] Use an in-repo font for test-multithread (#1218)
As Khaled's suggestion, hard-coded font paths was only for my own testing.
2018-10-03 21:26:58 +03:30
..
CMakeLists.txt [subset] add a fuzzer target for subset_get_all_codepoints method. (#987) 2018-04-17 16:21:22 +02:00
Makefile.am [subset] add a fuzzer target for subset_get_all_codepoints method. (#987) 2018-04-17 16:21:22 +02:00
README
hb-fuzzer.hh
hb-shape-fuzzer.cc [subset] Rename hb-fuzzer -> hb-shape-fuzzer. 2018-03-16 09:04:01 -07:00
hb-subset-fuzzer.cc [circleci] Fix some of warnings from clang-everything bot (#1211) 2018-10-02 21:39:19 +03:30
hb-subset-get-codepoints-fuzzer.cc [face] Introduce character-map API 2018-08-25 22:44:39 -07:00
main.cc [test] Use an in-repo font for test-multithread (#1218) 2018-10-03 21:26:58 +03:30
run-shape-fuzzer-tests.py [circleci] Fix "msan" and "everything" bots (#1205) 2018-10-02 00:16:08 +03:30
run-subset-fuzzer-tests.py [circleci] Fix "msan" and "everything" bots (#1205) 2018-10-02 00:16:08 +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