Lines Matching +full:oss +full:- +full:fuzz +full:- +full:project +full:- +full:name

1 # Fuzz testing
3 Each parser of the library (JSON, BJData, BSON, CBOR, MessagePack, and UBJSON) can be fuzz tested. …
19   rm -fr corpus_$FORMAT
21 …find json_test_data-$TEST_DATA_VERSION -size -5k -name "*.$FORMAT" -exec cp "{}" "corpus_$FORMAT" …
23 rm -fr json_test_data-$TEST_DATA_VERSION
31 To use libFuzzer, you need to pass `-fsanitize=fuzzer` as `FUZZER_ENGINE`. In the `tests` directory…
34 make fuzzers FUZZER_ENGINE="-fsanitize=fuzzer"
37 This creates a fuzz tester binary for each parser that supports these
42 Clang via Homebrew calling `brew install llvm` and add `CXX=$(brew --prefix llvm)/bin/clang` to the…
45 make fuzzers FUZZER_ENGINE="-fsanitize=fuzzer" CXX=$(brew --prefix llvm)/bin/clang
48 Then pass the corpus directory as command-line argument (assuming it is located in `tests`):
55 a file starting with `crash-`.
59 To use afl++, you need to pass `-fsanitize=fuzzer` as `FUZZER_ENGINE`. It will be replaced by a `li…
60 re-use the same code written for libFuzzer with afl++. Furthermore, set `afl-clang-fast++` as compi…
63 CXX=afl-clang-fast++ make fuzzers FUZZER_ENGINE="-fsanitize=fuzzer" 
69 afl-fuzz -i corpus_cbor -o out  -- ./parse_cbor_fuzzer 
75 ## OSS-Fuzz  section in Fuzz testing
77 The library is further fuzz-tested 24/7 by Google's [OSS-Fuzz project](https://github.com/google/os…
79 [build script](https://github.com/google/oss-fuzz/blob/master/projects/json/build.sh) for more info…
81 In case the build at OSS-Fuzz fails, an issue will be created automatically.