diff options
| author | Ben Harris <bjh21@bjh21.me.uk> | 2023-02-21 21:04:58 +0000 |
|---|---|---|
| committer | Ben Harris <bjh21@bjh21.me.uk> | 2023-02-23 11:34:32 +0000 |
| commit | 015bd1447472f82a5607ecb5fabaf25bf37cd4e2 (patch) | |
| tree | b9127e4e2cf30728548fc746b255a6c1fc14443f /fuzzpuzz.c | |
| parent | 80de73a6aa4c4e726860c492d2264d4958a56b0d (diff) | |
| download | puzzles-015bd1447472f82a5607ecb5fabaf25bf37cd4e2.zip puzzles-015bd1447472f82a5607ecb5fabaf25bf37cd4e2.tar.gz puzzles-015bd1447472f82a5607ecb5fabaf25bf37cd4e2.tar.bz2 puzzles-015bd1447472f82a5607ecb5fabaf25bf37cd4e2.tar.xz | |
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.
Diffstat (limited to 'fuzzpuzz.c')
| -rw-r--r-- | fuzzpuzz.c | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -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 <stdbool.h> |