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
Breakpoint not getting triggered in Solar sample #10527
Comments
This comment was originally written by @mhausner Can you run the VM with flags? If so, does this bug go away if you run the VM with: --optimization_counter_threshold=-1 |
This comment was originally written by podivilov@google.com Yes, with --optimization_counter_threshold=-1 everything works fine. |
Added Area-VM label. |
Removed Priority-Medium label. |
Set owner to @turnidge. |
Added Accepted label. |
I have verified that the bug still occurs, even after my recent fixes to debugging inlined functions. The function is clearly not being properly deoptimized in response to the new breakpoint. If I break in a sibling function single-step into the specified function, the breakpoint works after that point. So this is screwy. I will investigate with some tracing code on and see what's going on. |
We needed to deoptimize implicit closure functions. Fix is out for review. |
This issue was originally filed by podivilov@google.com
Open Solar sample in editor and run. Wait for a few seconds then set a breakpoint in SolarSystem.drawBackground (solar.dart:132). Breakpoint is not triggered.
The behavior depends on timing. If you set the breakpoint fast enough after the sample is loaded, it will be triggered.
The text was updated successfully, but these errors were encountered: