You've already forked openscreen
616a118d38
This updates content in README.md and breaks out some sections into separate files, to keep the length more manageable. Change-Id: I236ae43cd7323af8a11086ffe6c56ddb81b67a0c Reviewed-on: https://chromium-review.googlesource.com/c/openscreen/+/3028486 Reviewed-by: Jordan Bayles <jophba@chromium.org> Reviewed-by: Ryan Keane <rwkeane@google.com> Commit-Queue: mark a. foltz <mfoltz@chromium.org>
891 B
891 B
Building and running fuzzers
In order to build fuzzers, you need the GN arg use_libfuzzer=true. It's also
recommended to build with is_asan=true to catch additional problems. Building
and running then might look like:
gn gen out/libfuzzer --args="use_libfuzzer=true is_asan=true is_debug=false"
ninja -C out/libfuzzer some_fuzz_target
out/libfuzzer/some_fuzz_target <args> <corpus_dir> [additional corpus dirs]
The arguments to the fuzzer binary should be whatever is listed in the GN target
description (e.g. -max_len=1500). These arguments may be automatically
scraped by Chromium's ClusterFuzz tool when it runs fuzzers, but they are not
built into the target. You can also look at the file
out/libfuzzer/some_fuzz_target.options for what arguments should be used. The
corpus_dir is listed as seed_corpus in the GN definition of the fuzzer
target.