diff options
| author | Ben Harris <bjh21@bjh21.me.uk> | 2023-02-16 23:26:43 +0000 |
|---|---|---|
| committer | Ben Harris <bjh21@bjh21.me.uk> | 2023-02-16 23:26:43 +0000 |
| commit | a1f1d7c24713277a96c1f508cd3782e5aaf18c69 (patch) | |
| tree | 6462494829d2d41a8d7cde6483f82298424c30a7 /fuzzpuzz.c | |
| parent | 100cfd2e994fe870af1bd247097dfc105291c1bd (diff) | |
| download | puzzles-a1f1d7c24713277a96c1f508cd3782e5aaf18c69.zip puzzles-a1f1d7c24713277a96c1f508cd3782e5aaf18c69.tar.gz puzzles-a1f1d7c24713277a96c1f508cd3782e5aaf18c69.tar.bz2 puzzles-a1f1d7c24713277a96c1f508cd3782e5aaf18c69.tar.xz | |
Update and expand comment at the head of fuzzpuzz
It now correctly describes what fuzzpuzz does. It also provides an
example of how to use it with AFL++.
Diffstat (limited to 'fuzzpuzz.c')
| -rw-r--r-- | fuzzpuzz.c | 15 |
1 files changed, 12 insertions, 3 deletions
@@ -4,9 +4,18 @@ /* * The idea here is that this front-end supports all back-ends and can - * feed them save files. This tests the deserialiser, the code for - * loading game descriptions, and the processing of move strings, - * without all the tedium of actually rendering anything. + * feed them save files. It then asks the back-end to draw the puzzle + * (through a null drawing API) and reserialises the state. This + * tests the deserialiser, the code for loading game descriptions, the + * processing of move strings, the redraw code, and the serialisation + * routines, but is still pretty quick. + * + * To use AFL++ to drive fuzzpuzz, you can do something like: + * + * CC=afl-cc cmake -B build-afl + * cmake --build build-afl --target fuzzpuzz + * mkdir fuzz-in && ln icons/*.sav fuzz-in + * afl-fuzz -i fuzz-in -o fuzz-out -x fuzzpuzz.dict -- build-afl/fuzzpuzz */ #include <stdbool.h> |