random action fuzzer #69
Merged
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
evanrichter
force-pushed
the
fuzz-harness
branch
from
b5b7a8e to
0c116a4
Compare
|
Thanks a lot for this PR and sorry for the delay in merging! |
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 cargo-fuzz harness tests the following actions randomly, making sure each call is safe before invoking linked-list-allocator APIs:
allocate_first_fitdeallocateextendIt also initializes the Heap with a random size.
Besides the harness, I added a
#[cfg(fuzzing)]-gated debug printer for Heap which helped when adding buffering to extend. Since it's not needed for actual fuzzing (the harness hasDEBUG = falseby default), I can remove that if requested!