Draft
Conversation
MiranDMC
force-pushed
the
memory_access_validation
branch
from
f61fd3e to
59a26cd
Compare
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.
All blocks allocated with allocate_memory command now have added 4 byte marker to the front and back (pointer returned to user points after data between them). During release of the allocated block markers are tested. If modified memory corruption error is reported.
Write, read, copy, compare memory commands now are checking if accessed memory region crosses with any of known allocated block, if so check is performed to verify if the accessed range lies entirely withing the memory block.
Checks are not active if global strict mode is disabled or script is in legacy mode.