mirror of
https://github.com/ghostty-org/ghostty.git
synced 2026-04-15 12:02:39 +00:00
2.0 KiB
2.0 KiB
AFL++ Fuzzer for Libghostty
- Build all fuzzer with
zig build - The list of available fuzzers is in
build.zig(search forfuzzers). - Run a specific fuzzer with
zig build run-<name>(e.g.zig build run-parser) - Corpus directories follow the naming convention
corpus/<fuzzer>-<variant>(e.g.corpus/parser-initial,corpus/stream-cmin). - Do NOT run
afl-tminunless explicitly requested — it is very slow. - After running
afl-cmin, runcorpus/sanitize-filenames.shbefore committing to replace colons with underscores (colons are invalid on Windows NTFS).
Important: stdin-based input
The instrumented binaries (afl.c harness) read fuzz input from stdin,
not from a file argument. This affects how you invoke AFL++ tools:
-
afl-fuzz: Uses shared-memory fuzzing automatically;@@works because AFL writes directly to shared memory, bypassing file I/O. -
afl-showmap: Must pipe input via stdin, not@@:cat testcase | afl-showmap -o map.txt -- zig-out/bin/fuzz-stream -
afl-cmin: Do not use@@. RequiresAFL_NO_FORKSRV=1with the bash version due to a bug in the Pythonafl-cmin(AFL++ 4.35c):AFL_NO_FORKSRV=1 /opt/homebrew/Cellar/afl++/4.35c/libexec/afl-cmin.bash \ -i afl-out/fuzz-stream/default/queue -o corpus/stream-cmin \ -- zig-out/bin/fuzz-stream
If you pass @@ or a filename argument, afl-showmap/afl-cmin
will see only ~4 tuples (the C main paths) and produce useless results.
Replaying crashes
Use replay-crashes.nu (Nushell) to list or replay AFL++ crash files.
- List all crash files:
nu replay-crashes.nu --list - JSON output (for structured processing):
nu replay-crashes.nu --jsonReturns an array of objects withfuzzer,file,binary, andreplay_cmd. - Filter by fuzzer:
nu replay-crashes.nu --list --fuzzer stream - Replay all crashes:
nu replay-crashes.nuPipes each crash file into its fuzzer binary via stdin and exits non-zero if any crashes still reproduce.