fuzz: add example fuzzing targets #1949
Open
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
rnxpyke
force-pushed
the
fuzz/1898
branch
2 times, most recently
from
00bb0bf to
95ca274
Compare
|
hm, seems like we can use an ENV var in the fuzzing call: rust-fuzz/cargo-fuzz#384 |
|
@elijah-potter would be nice to know what you think about this approach |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
this PR adds
cargo-fuzzfuzzing targets for harper parsers.Ideally, we wouldn't just fuzz the parser, but also the linting step with the resulting tokens to cover the
harper-corecode.Notice that I had to turn of
lto = truein the workpace Cargo.toml, so maybe we want to figure out how fuzzing can coexist with lto before merging.Related: #1898 #1948
Demo
Example of fuzzing run finding a crash: https://asciinema.org/a/ShdOcwthkwwn72JyGpRk9emOu
Checklist