WIP: Add fuzz test for PrefilledTransaction #873
Closed
Conversation
This file contains 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
Add a simple deserialization fuzz test for `PrefilledTransaction`.
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.
This is only needed if #1088 merges.
Add a simple deserialization fuzz test for
PrefilledTransaction.I'm totally new to fuzzing. Is the thing being checked, (in for example
deser_net_msg.rs) that there is no input data that will cause the deserialization to crash the process?If that is the case then is the code in this PR what is meant by the issue: #460?
Do we want a fuzz file for each
pub structinbip152.rs?