Stuff to think about (or do) before fuzzing (optional) - Are external libraries being used? - Should or shouldn't they be fuzzed? - Are there any "developer tools" (without expensive GUI code etc.) - Use tmpfs to reduce disk usage? - Profile fuzz "victim": valgrind --tool=cachegrind ... cg_annotate cachegrind.out.59446 (or use KCachegrind) - Optimize expensive but required parts - #ifdef out "useless" parts - #ifdef out "fuzz barriers" (checksums, required values ...) - Insert exit() after interesting parts