Repository navigation
fuzz: traverse while mutating, check capacity, add a pool harness - #12
Merged
aotodev merged 1 commit intoSep 29, 2026
Merged
Conversation
aotodev
deleted the
7-fuzz-harness-blind-to-iterator-and-capacity-bugs
branch
September 29, 2026 19:48
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.
fuzz_multislab only counted blocks from a fresh begin() and accepted any
nullptr under a cap, so the iterator and refill bugs got past it. It now
walks while releasing and allocating, holds allocate_at iterators across
operations, and requires allocation to succeed iff the cap leaves room.
fuzz_pool drives inserts, stored-iterator erases, erase-while-iterating
sweeps and clones over a payload that traps use after destruction.
Both catch the old bugs within seconds on the pre-fix commits.
Closes #7