Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a
test/fuzz-libghosttywhich is a standalonezig buildtarget for building an AFL++ instrumented executable for fuzzing the libghostty-vt parser. I also added apkg/afl++(based on zig-afl-kit) so instrumenting objects and using AFL++ is a bit easier.Fuzzing
libghostty-vt's parser is as easy aszig build run, but see the README for a lot more details. I ran the fuzzer for ~14 hours total and only found one crash #11088. I'm pretty confident at this point our Parser layer isn't obviously crash-able, but need to instrument more places to fuzz.We don't use Zig's built-in fuzzing yet because as of 0.15 (our current stable), it isn't ready and AFL++ is an industry proven tool to do this.