Uh oh!
There was an error while loading. Please reload this page.
[release/6.0] [wasm][debugger] Avoiding assert on mono runtime - #62816
Conversation
ghost
commented
Dec 14, 2021
Tagging subscribers to this area: @thaystg Issue DetailsBackport of #62601 to release/6.0 /cc @thaystg Customer ImpactAs 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. TestingUnit tests and manual tests on Blazor. RiskLow Risk, only checking the debugId of the assembly and getting the correct one before send to debugger-agent.
|
ghost
commented
Dec 14, 2021
Tagging subscribers to this area: @thaystg Issue DetailsBackport of #62601 to release/6.0 /cc @thaystg Customer ImpactAs 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. TestingUnit tests and manual tests on Blazor. RiskLow Risk, only checking the debugId of the assembly and getting the correct one before send to debugger-agent.
|
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.