Modified the FreeSpaceModifier to mark patch bytes written to the binary as not free #409
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.
One sentence summary of this PR (This should go in the CHANGELOG!)
Change
FreeSpaceModifier
&PartialFreeSpaceModifier
behavior: an optional stub that isn't free space can be provided and fill-bytes for free space can be specified.Link to Related Issue(s)
N/A.
Please describe the changes in your request.
This changes the signature and intended behavior of the configs for
FreeSpaceModifier
andPartialFreeSpaceModifier
. Each modifier now allows for injecting a "stub" at the beginning of the targeted code to be freed. This stub is not included in theFreeSpace
. The config's "fill" parameter is now the data pattern used to overwrite the bytes that fall in theFreeSpace
.Anyone you think should look at this, specifically?
@rbs-afflitto, @rbs-alexr.
Optionally: @rbs-jacob, @EdwardLarson .