fix: Allow Windows CFI to underflow #645
Merged
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.
We have seen some SaveNonVolatile unwind operations underflow the current stack frame, so they are saving/loading registers into the callers stack frame.
For example
VCRUNTIME140.dll!__C_specific_handler
can do this.Its full Unwind Operations look like this:
We previously used saturating_sub to clamp these offsets to 0, meaning things are loaded from the current stack frame instead of from the callers frame. Now we correctly generate ASCII CFI for these Unwind Codes.
This fixes one pre-condition of #638, namely that it depends on
$rbp
which is loaded from the above unwind codes, thus outside its own stack frame.