Skip to content

[release/9.0-staging] [debugger] Fix debugging a x86 app in mixed mode #114077

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

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 31, 2025

Backport of #114075 to release/9.0-staging

/cc @thaystg

Customer Impact

  • Customer reported
  • Found internally

https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2428652
When a customer is trying to debug a x86 app from an AMD64, all the locals that are floating point are not displayed correctly and also the behavior of the program is wrong while debugging.
The runtime was getting the context from OS without asking for all the needed data, with that we are saving the wrong context, missing the float values, and restoring it also wrongly without this values, making the program work incorrectly and also the debugger couldn't show the correct values.

Regression

  • Yes
  • No

Testing

Manually tested.

Risk

Low risk, we are only getting the context with more fields for x86 machines.

Copy link
Contributor

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

@github-actions github-actions bot force-pushed the backport/pr-114075-to-release/9.0-staging branch from a11d532 to a3133a0 Compare March 31, 2025 18:23
@carlossanlop
Copy link
Contributor

Friendly reminder that code complete is on April 14th for the May Release. If you'd like to get this change included in that release, please get a Tactics approval and merge this PR before that date.

@thaystg thaystg marked this pull request as ready for review April 10, 2025 12:51
@Copilot Copilot AI review requested due to automatic review settings April 10, 2025 12:51
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. we will take for consideration in 9.0.x

@jeffschwMSFT jeffschwMSFT added the Servicing-consider Issue for next servicing release review label Apr 11, 2025
@jeffschwMSFT jeffschwMSFT added this to the 9.0.x milestone Apr 11, 2025
@thaystg thaystg requested a review from tommcdon April 11, 2025 16:39
@carlossanlop
Copy link
Contributor

Friendly reminder that code complete for the May release is next Monday April 14th. If you want this change included in that release, please take it to Tactics and merge the PR before EOD Monday.

@jeffschwMSFT jeffschwMSFT added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Apr 14, 2025
@jeffschwMSFT jeffschwMSFT modified the milestones: 9.0.x, 9.0.5 Apr 14, 2025
@thaystg thaystg merged commit b2c8247 into release/9.0-staging Apr 14, 2025
96 of 100 checks passed
@thaystg thaystg deleted the backport/pr-114075-to-release/9.0-staging branch April 14, 2025 15:40
@github-actions github-actions bot locked and limited conversation to collaborators May 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants