Uh oh!
There was an error while loading. Please reload this page.
[wasm][debugger] fixing setting a breakpoint in an invalid IL offset after hotreload - #75561
Conversation
ghost
commented
Sep 13, 2022
Tagging subscribers to this area: @thaystg Issue DetailsIt's not possible to add a test case because it is a concurrency issue, let me try to explain:
The fix was to remove the exception throw and check the return of the set breakpoint function. Fixes #75492
|
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Ankit Jain <radical@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Ankit Jain <radical@gmail.com>
ghost
commented
Sep 13, 2022
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIt's not possible to add a test case because it is a concurrency issue, let me try to explain:
The fix was to remove the exception throw and check the return of the set breakpoint function. Fixes #75492
|
thaystg
commented
Sep 13, 2022
/backport to release/7.0 |
Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3048571879 |
It's not possible to add a test case because it is a concurrency issue, let me try to explain:
The fix was to remove the exception throw and check the return of the set breakpoint function.
Fixes#75492