Fix reported string issue in ildasm#124108
Merged
AaronRobinsonMSFT merged 4 commits intodotnet:mainfrom Feb 7, 2026
Merged
Conversation
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @dotnet/jit-contrib |
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes an ILDASM/metainfo UTF-16 → UTF-8 conversion failure path that could write past the end of the destination buffer, addressing a regression introduced during %S removal work (#78894).
Changes:
- Corrects the error-path null-termination in
ConvertToUtf8to avoid out-of-bounds writes whenWideCharToMultiBytefails.
jkotas
reviewed
Feb 6, 2026
jkotas
approved these changes
Feb 6, 2026
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
2 participants
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.
Introduced in #78894
Fixes #124073