aboutsummaryrefslogtreecommitdiff
path: root/samegame.c
diff options
context:
space:
mode:
authorBen Harris <bjh21@bjh21.me.uk>2023-02-20 21:51:18 +0000
committerBen Harris <bjh21@bjh21.me.uk>2023-02-23 11:34:20 +0000
commit5ba227031c865aff55fdaf7c9a1b0e8abcbbabc4 (patch)
tree6bef4680923990c03ad4bcaa55849d8fad999884 /samegame.c
parentecd868ac6e7ab3df4984ff29a16c7158339611a3 (diff)
downloadpuzzles-5ba227031c865aff55fdaf7c9a1b0e8abcbbabc4.zip
puzzles-5ba227031c865aff55fdaf7c9a1b0e8abcbbabc4.tar.gz
puzzles-5ba227031c865aff55fdaf7c9a1b0e8abcbbabc4.tar.bz2
puzzles-5ba227031c865aff55fdaf7c9a1b0e8abcbbabc4.tar.xz
Rough support for fuzzing with libFuzzer
For AFL++ and Honggfuzz, our approach is to build a standard fuzzpuzz binary with extra hooks for interacting with an external fuzzer. This works well for AFL++ and tolerably for Honggfuzz. LibFuzzer, though, provides its own main() so that the resulting program has a very different command-line interface from the normal one. Also, since libFuzzer is a standard part of Clang, we can't decide whether to use it based on the behaviour of the compiler. So what I've done, at least for now, is to have CMake detect when we're using Clang and in that case build a separate binary called "fuzzpuzz-libfuzzer" which is built with -fsanitize=fuzzer, while the ordinary fuzzpuzz is built without. I'm not sure if this is the right approach, though.
Diffstat (limited to 'samegame.c')
0 files changed, 0 insertions, 0 deletions