| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| fonts/ | 03-May-2024 | - | 2 | 2 | ||
| CMakeLists.txt | D | 03-May-2024 | 1.2 KiB | 28 | 22 | |
| Makefile.am | D | 03-May-2024 | 1.5 KiB | 64 | 51 | |
| README | D | 03-May-2024 | 967 | 22 | 19 | |
| hb-fuzzer.hh | D | 03-May-2024 | 110 | 5 | 3 | |
| hb-shape-fuzzer.cc | D | 03-May-2024 | 1.3 KiB | 48 | 38 | |
| hb-subset-fuzzer.cc | D | 03-May-2024 | 2 KiB | 80 | 64 | |
| main.cc | D | 03-May-2024 | 485 | 24 | 19 | |
| run-shape-fuzzer-tests.py | D | 03-May-2024 | 2.3 KiB | 100 | 71 | |
| run-subset-fuzzer-tests.py | D | 03-May-2024 | 1.3 KiB | 46 | 30 |
README
1In order to build the fuzzer one needs to build HarfBuzz and 2harfbuzz/test/fuzzing/hb-fuzzer.cc with: 3 - Using the most recent Clang 4 - With -fsanitize=address (or =undefined, or a combination) 5 - With -fsanitize-coverage=edge[,8bit-counters,trace-cmp] 6 - With various defines that limit worst case exponential behavior. 7 See FUZZING_CPPFLAGS in harfbuzz/src/Makefile.am for the list. 8 - link against libFuzzer 9 10To run the fuzzer one needs to first obtain a test corpus as a directory 11containing interesting fonts. A good starting point is inside 12harfbuzz/test/shaping/fonts/fonts/. 13Then, run the fuzzer like this: 14 ./hb-fuzzer -max_len=2048 CORPUS_DIR 15Where max_len specifies the maximal length of font files to handle. 16The smaller the faster. 17 18For more details consult the following locations: 19 - http://llvm.org/docs/LibFuzzer.html or 20 - https://github.com/google/libfuzzer-bot/tree/master/harfbuzz 21 - https://github.com/harfbuzz/harfbuzz/issues/139 22