[DEPENDENCY] BlitzForge bump — crash-handler bounds fix (review finding)#550
Merged
Conversation
Picks up blitz-forge#87: the quality-gate review of the flake fix (#549 / blitz-forge#86) found the new seTranslator diagnostics sprintf'd a 110-char regs line into a 96-byte stack buffer -- a guaranteed 15-byte OOB write on the crash path. All handler formatting is now snprintf-bounded, and the generated-image dump clamps to the committed region it actually reads. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Routine bump picking up blitz-forge#87: the quality-gate review of #549's compiler fix found that the new
seTranslatorcrash diagnostics formatted a 110-char registers line into a 96-byte stack buffer — a guaranteed 15-byte out-of-bounds write on the crash path itself. All crash-handler formatting is nowsnprintf-bounded, and the generated-image hex dump clamps to the committed region it reads.No engine source changes. Local sanity: engine compile clean, ItemsTest green; BlitzForge suite green upstream (includes the divzero diagnostic contract that exercises the handler end-to-end).
🤖 Generated with Claude Code