Skip to content

detect fragmentation when fuzzing #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 14, 2022

Conversation

evanrichter
Copy link
Contributor

after a single fuzz run, we already free all allocations, so this adds an assertion that we can indeed allocate the full span of the Heap.

This should be a good regression test, as it does catch the fragmentation issue #66 when on the affected version. (and the current impl passes!)

Copy link
Member

@phil-opp phil-opp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot!

@phil-opp phil-opp merged commit f7c2d8e into rust-osdev:main Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants