Handle multiple flag registers #25
Merged
Conversation
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
This was referenced Apr 3, 2024
Closed
stephen-f0
force-pushed
the
feature/handle-multiple-flag-registers
branch
from
02a53e4 to
eb68332
Compare
sam-f0
approved these changes
Apr 5, 2024
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.
Support for architectures to define multiple flag registers with an associated bitmask.
Fixes an LLDB oddity where running on 64-bit Windows presents "eflags" compared to Linux where "rflags" is presented. Can also be used to define multiple different flag registers with differing bitmasks which would all be presented in the UI.
Handles cases where the defined flags register(s) are not exposed in the LLDB register dictionary. Fixes #23