harfbuzz/test/fuzzing
Ebrahim Byagowi 30c059a978
[test] minor, fix -Weverything bot
2019-05-11 18:48:41 -04:00
..
fonts Fix sanitize fail of extension sublookups 2019-05-10 16:03:20 -07:00
CMakeLists.txt
Makefile.am [valgrind] Use libtool and support run-subset-fuzzer-tests (#1668) 2019-04-28 11:54:07 -07:00
README
hb-fuzzer.hh
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 [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