eBookReaderSwitch/thirdparty/harfbuzz/test/fuzzing
Moroni Granja 98d9d7be17 Squashed 'mupdf/' content from commit 340abaf66
git-subtree-dir: mupdf
git-subtree-split: 340abaf66f43a04477866e5df8ba9726709f43f4
2019-10-30 13:48:08 -03:00
..
CMakeLists.txt Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
Makefile.am Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
README Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
hb-fuzzer.hh Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
hb-shape-fuzzer.cc Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
hb-subset-fuzzer.cc Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
hb-subset-get-codepoints-fuzzer.cc Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
main.cc Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
run-shape-fuzzer-tests.py Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
run-subset-fuzzer-tests.py Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03: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