Add the missing changelog entry for #84 - #86
Merged
Merged
Conversation
PR #84 widened the heap detectors to four more allocators but never got a changelog entry. It is user-visible twice over: more of the guest's memory is guarded, and real PhxAss stops being silent under --sanitize because the new coverage found a genuine two-byte over-read of its own timerequest. Anyone running the corpus sweep needs to know that one report is expected rather than a regression. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AKBJRT9j5APTyKyZtj8f23
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.
#84 widened the heap detectors to four more allocators (
AllocateTagItems,AllocDosObject,CreateIORequest,CreateMsgPortand their frees) but never got a changelog entry.It's user-visible twice over, which is why it's worth backfilling rather than skipping:
FileInfoBlock,RDArgs,MsgPortorTagItemarray volamos handed it is now caught.--sanitize, because the new coverage immediately found a genuine two-byte over-read of its own 40-bytetimerequest. Anyone running the corpus sweep needs to know that report is expected, not a regression they've introduced.Also notes what still isn't covered (
exec.library/Allocate, where a C runtime'smallocsub-allocates — #83's main body).mkdocs build --strictclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01AKBJRT9j5APTyKyZtj8f23