-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add IMAGE_FILE_MACHINE_ARM64X and IMAGE_FILE_MACHINE_ARM64EC #2858
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can also get IMAGE_FILE_MACHINE_ARM64X
and IMAGE_FILE_MACHINE_ARM64EC
when you are debugging in x64 emulation on arm64 machines. For a complete fix you should add logic so when you are in SOS_TARGET_X64
and you see either of them then load the x64 machine
Then this is not going to work - if we can get such value in both arm64 and x64 scenarios we might need something different to identify process arch. |
I think it will work. If SOS is running on x64 (either real or emulated), both SOS_TARGET_AMD64 and SOS_TARGET_ARM64 are defined so putting the checks for those two processor types in the SOS_TARGET_ARM64 section should work. |
Should work the way Juan has it now. |
|
I am closing old PRs that have had no progress in a long time. You are welcome to resume the work any time and open a new PR. |
0e85942
to
0fb0a96
Compare
0fb0a96
to
9e6e688
Compare
@hoyosjs can you review? |
The changes requested have been fixed.
87d0620
to
756fb9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo the thing.
Co-authored-by: David Mason davmason@microsoft.com