-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[wasm][debugger] fixing setting a breakpoint in an invalid IL offset after hotreload #75561
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
Conversation
|
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
|
Co-authored-by: Ankit Jain <[email protected]>
Co-authored-by: Ankit Jain <[email protected]>
|
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
|
|
/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