You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…flowgraph
Debugger will retrieve the saved context object when looking for IsAtAsyncJump(). The saved context object does not match the context level if setting breakpoint on "break" statement.
It is because when flowgraph builds break statement, DebugStepCheck was put after context object was restored to its parent. Then activation frame got the parent context when pausing at breakpoint.
Bug: #36622
Change-Id: I07508eb42ab102f9697797ef15f914de8bd1af65
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/100087
Commit-Queue: Zichang Guo <zichangguo@google.com>
Reviewed-by: Ryan Macnak <rmacnak@google.com>
Reviewed-by: Ben Konyi <bkonyi@google.com>
@duzenko the fix is in the Dart SDK, not the VS Code extension. Looking at the commit above, it should be in 2.3.1-dev.0.0 which you can get from https://dart.dev/tools/sdk/archive if you don't mind using a Dev release in the meantime.
If you're using Flutter, you'll need to switch to the Flutter branch that includes a Dart SDK that has this fix (master will, though I'm not sure about dev).
This was raised at Dart-Code/Dart-Code#1617. I can reproduce using today's nightly build with just this Dart script (run directly - no Flutter):
Some observations from @kinex:
Few observations:
Here's the crash:
(@a-siva @bkonyi)
The text was updated successfully, but these errors were encountered: