From 015bd1447472f82a5607ecb5fabaf25bf37cd4e2 Mon Sep 17 00:00:00 2001 From: Ben Harris Date: Tue, 21 Feb 2023 21:04:58 +0000 Subject: Don't give the libFuzzer version of fuzzpuzz a special name I've changed my mind already. The other versions of fuzzpuzz all have different command-line interfaces anyway, so I think the best approach is to just accept that and decide that precisely how fuzzpuzz works isn't a defined API. Fuzzing is inherently not an end-user activity, so I think it's acceptable to make it a bit inconsistent. This means that in Clang builds you get the non-libFuzzer version of fuzzpuzz by default (so you can use it with other fuzzers), but if you turn on WITH_LIBFUZZER then you'll get the libFuzzer version instead. --- fuzzpuzz.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'fuzzpuzz.c') diff --git a/fuzzpuzz.c b/fuzzpuzz.c index 5fcd01f..3fb632e 100644 --- a/fuzzpuzz.c +++ b/fuzzpuzz.c @@ -27,11 +27,11 @@ * You can also use libFuzzer, though it's not really a good fit for * Puzzles. The experimental forking mode seems to work OK: * - * CC=clang cmake -B build-clang - * cmake --build build-clang --target fuzzpuzz-libfuzzer + * CC=clang cmake -B build-clang -DWITH_LIBFUZZER=Y + * cmake --build build-clang --target fuzzpuzz * mkdir fuzz-corpus && ln icons/''*.sav fuzz-corpus - * build-clang/fuzzpuzz-libfuzzer -fork=1 -ignore_crashes=1 \ - * -dict=fuzzpuzz.dict fuzz-corpus + * build-clang/fuzzpuzz -fork=1 -ignore_crashes=1 -dict=fuzzpuzz.dict \ + * fuzz-corpus */ #include -- cgit v1.1