[release/9.0-preview7] [wasm][debugger] Fix debugging when JMC is enabled #105815
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
ghost
added
the
|
Tagging subscribers to this area: @thaystg |
ilonatommy
approved these changes
Aug 1, 2024
|
If we are taking other changes in p7 this one fixes a regression in the old debugger. |
lewing
approved these changes
Aug 1, 2024
lewing
added
Servicing-approved
jeffschwMSFT
approved these changes
Aug 1, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 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.
Backport of #105756 to release/9.0-preview7
/cc @thaystg
Customer Impact
Breakpoints does not work when WASM debugging in VSCode and in VS (if new debugger is disabled).
Regression
#103755
Testing
Manually tested.
Risk
Low risk.