Fix GDB MI register parsing for XMM/YMM and unavailable values#1022
Merged
Fix GDB MI register parsing for XMM/YMM and unavailable values#1022
Conversation
…ilable values ParseGdbValue now handles three additional cases from GDB's -data-list-register-values output: - <unavailable> markers (returned for inaccessible registers) - XMM composite structs (extracts uint128 field) - YMM composite structs (combines v2_int128 high/low fields) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Member
Author
|
Fixes: #1021 |
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
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.
Summary
<unavailable>register values gracefully (return 0 instead of logging an error)uint128 = 0x...fieldv2_int128 = {0xHIGH, 0xLOW}fields into a 256-bit valueTest plan
🤖 Generated with Claude Code