Workaround ExceptionFlags change in NT #2265
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.
...by allowing flags other than
EXCEPTION_NONCONTINUABLE
to be set byRaiseException
. This should unblock CI on the new Server 2022 VMs, for whichRaiseException
sets a new flag indicating that the exception originated in software. (This also reproduces locally for me on Windows 11.)This mirrors the STL changes from the internal MSVC-PR-356899.
(Tagging this as high priority since we already merged the internal PR to unblock CI.)