DescriptionFix causal_async_star_stack_contents_test with optimization-counter-threshold=5
There was an off by one error when generating the causal async stack trace
in the debugger. We were always adding one more frame pass the sentinel frame.
This frame is always _Closure.call which is filtered out by the debugger
already. However when --optimization-counter-threshold=5, _Closure.call was
inlined and we ended up appending the inliner to the stack trace. The
inliner is not filtered out by the debugger so we got an extra frame in
the stack trace.
Fixes #28861
BUG=
R=fschneider@google.com
Committed: https://github.com/dart-lang/sdk/commit/6a312d429b3b554b7b2281c7c140bc0dca40bc76
Patch Set 1 #Patch Set 2 : rebase #
Messages
Total messages: 6 (3 generated)
|