Natvis: trim leading/trailing whitespace from DisplayString XML text#1571
Merged
Merged
Conversation
WardenGnaw
approved these changes
May 27, 2026
Visual Studio trims whitespace from DisplayString inner XML text before processing. MIEngine did not, causing multi-line DisplayStrings to render as blank on GDB/LLDB — the leading newline and indentation made the display appear empty in the variables panel. Fix: call format.Trim() at the top of FormatValue() before processing.
WardenGnaw
force-pushed
the
displaystring_multiline_fix
branch
from
1207412 to
afc93f3
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
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.
Visual Studio trims whitespace from DisplayString inner XML text before processing. MIEngine did not, causing multi-line DisplayStrings to render as blank on GDB/LLDB — the leading newline and indentation made the display appear empty in the variables panel.
Fix: call format.Trim() at the top of FormatValue() before processing.