[release/6.0] [wasm][debugger] Avoiding assert on mono runtime #62816
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 #62601 to release/6.0
/cc @thaystg
Customer Impact
As VS tries to evaluate a lot of things while hover the mouse on variables while debugging, could be causing assert on runtime in the case of trying to evaluate in a static class that is in a loaded assembly but not added any breakpoint on it.
Testing
Unit tests and manual tests on Blazor.
Risk
Low Risk, only checking the debugId of the assembly and getting the correct one before send to debugger-agent.