-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Column breakpoints not working - breaking as if they were just line breakpoints #51563
Comments
Fyi @bkonyi |
//cc @derekxu16 |
If I try to set the inline breakpoint before starting the debug session, the breakpoint incorrectly acts like a line breakpoint. But inline breakpoints do work if I follow the following procedure:
I tried setting an inline breakpoint in a similar JavaScript program before starting the debug session, and the breakpoint did correctly behave as an inline breakpoint, so I think something can be changed in the Dart Code extension to fix that flow. Do you mind looking into this when you get the chance @DanTup? |
I see the same behaviour described above, but I'm not sure how the VS Code extension can fix this - the requests to the VM Service are the same in both cases (allowing for the difference in code when adding an earlier breakpoint). It seems like the VM might be doing things incorrectly if the breakpoint is set before the script is loaded - but there's no way VS Code can wait before sending the breakpoint, because by then it will have been missed. Here's the VM call for the breakpoint that isn't working right, which shows the correct column (as does the response from the VM).
What's been weirder, is that if I add an additional Then now the breakpoint happens after all of the calls on that line instead of before: Again, the VM service call looks fine - line 3, column 21. |
Fix works great, thanks @derekxu16! |
While working on breakpoint resolution, I noticed that column breakpoints seem to behave as if they had no column specified.
Given the code:
And a column breakpoint added in the middle of all of the
a()
calls:When I run, the debugger resolves and breaks on the innermost call to
a()
as if it was just a standard line breakpoint:Here's the relevant log with annotations:
The full log is here:
full_log.txt
The text was updated successfully, but these errors were encountered: