-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[vm] Rework awaiter stack unwinding.
The main contribution of this CL is unification of disparate handling of various functions like `Future.timeout`, `Future.wait`, `_SuspendState.createAsyncCallbacks` and `_SuspendState._createAsyncStarCallback` into a single `@pragma('vm:awaiter-link')` which allows Dart developers to specify where awaiter unwinder should look for the next awaiter. For example this allows unwinding to succeed for the code like this: Future<int> outer(Future<int> inner) { @pragma('vm:awaiter-link') final completer = Completer<int>(); inner.then((v) => completer.complete(v)); return completer.future; } This refactoring also ensures that we preserve information (including Function & Code objects) required for awaiter unwinding across all modes (JIT, AOT and AOT with DWARF stack traces). This guarantees users will get the same information no matter which mode they are running in. Previously we have been disabling awaiter_stacks tests in some AOT modes - which led to regressions in the quality of produced stacks. This CL also cleans up relationship between debugger and awaiter stack returned by StackTrace.current - which makes stack trace displayed by debugger (used for stepping out and determinining whether exception is caught or not) and `StackTrace.current` consistent. Finally we make one user visible change to the stack trace: awaiter stack will no always include intermediate listeners created through `Future.then`. Previously we would sometimes include these listeners at the tail of the stack trace, which was inconsistent. Ultimately this means that code like this: Future<int> inner() async { await null; // asynchronous gap print(StackTrace.current); // (*) return 0; } Future<int> outer() async { int process(int v) { return v + 1; } return await inner().then(process); } void main() async { await outer(); } Produces stack trace like this: inner <asynchronous suspension> outer.process <asynchronous suspension> outer <asynchronous suspension> main <asynchronous suspension> And when stepping out of `inner` execution will stop at `outer.process` first and the next step out will bring execution to `outer` next. Fixes #52797 Fixes #52203 Issue #47985 TEST=ci Bug: b/279929839 CoreLibraryReviewExempt: CL just adds @pragma to facilitate unwinding Cq-Include-Trybots: luci.dart.try:vm-aot-linux-product-x64-try,vm-aot-linux-debug-x64-try,vm-aot-linux-release-x64-try,vm-aot-obfuscate-linux-release-x64-try,vm-aot-dwarf-linux-product-x64-try Change-Id: If377d5329d6a11c86effb9369dc603a7ae616fe7 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/311680 Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Slava Egorov <vegorov@google.com>
- Loading branch information
Showing
49 changed files
with
1,609 additions
and
1,224 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,127 @@ | ||
# Awaiter Stack Traces | ||
|
||
One of the common challenges associated with debugging asynchronous code is that stack traces do not reference the code which led to the exception. The context is lost when execution cross asynchronous gap. | ||
|
||
Consider the following code: | ||
|
||
```dart | ||
Future<int> inner() async { | ||
await null; // asynchronous gap | ||
print(StackTrace.current); // (*) | ||
return 0; | ||
} | ||
Future<int> outer() async { | ||
int process(int v) { | ||
return v + 1; | ||
} | ||
return await inner().then(process); | ||
} | ||
void main() async { | ||
await outer(); | ||
} | ||
``` | ||
|
||
Producing synchronous stack trace at the line marked `(*)` will yield the following: | ||
|
||
``` | ||
#0 inner | ||
#1 _SuspendState._createAsyncCallbacks.thenCallback | ||
#2 _RootZone.runUnary | ||
#3 _SuspendState._awaitNotFuture.run | ||
#4 _microtaskLoop | ||
#5 _startMicrotaskLoop | ||
#6 _startMicrotaskLoop | ||
#7 _runPendingImmediateCallback | ||
#8 _RawReceivePort._handleMessage | ||
``` | ||
|
||
Only a single frame corresponds to user code (`#0 inner`) and the rest are `dart:async` internals. Nothing in this stack trace mentions `outer` or `main`, which called `inner`. This makes diagnosing issues based on a stack trace much harder. | ||
|
||
To address this problem runtime system augments synchronous portion of the stack trace with an _awaiter stack trace_. Each awaiter frame represents a closure or a suspended `async` function which will be invoked when the currently running asynchronous computation completes. | ||
|
||
This support allows runtime system to produce the following output for the example given above: | ||
|
||
``` | ||
#0 inner | ||
<asynchronous suspension> | ||
#1 outer.process | ||
<asynchronous suspension> | ||
#2 outer | ||
<asynchronous suspension> | ||
#3 main | ||
<asynchronous suspension> | ||
``` | ||
|
||
## Algorithm | ||
|
||
To recover awaiter stack trace runtime follows through a chain of `_Future`, `_StreamController` and `SuspendState` objects. The following diagram illustrates the path it takes to produce asynchronous stack trace in our initial example: | ||
|
||
![Heap structure used for unwinding](awaiter_stack_unwinding.png) | ||
|
||
Each awaiter frame is a pair of `(closure, nextFrame)`: | ||
|
||
* `closure` is a listener which will be invoked when the future this frame is waiting on completes. | ||
* This might be one of the callbacks associated with [suspendable functions](async.md) internals, e.g. `_SuspendState.thenCallback` which resumes execution after the `await`. | ||
* `next` is an object representing the next awaiter frame, which is waiting for the completion of this awaiter frame. | ||
|
||
Unwinding rules can be summarised as follows: | ||
|
||
* If at any point `closure` has a captured variable marked with `@pragma('vm:awaiter-link')` variable then the value of that variable will be used as `nextFrame`. | ||
* If `nextFrame` is a `_SuspendState` then `_SuspendState.function_data` gives us `_FutureImpl` or `_AsyncStarStreamController` to look at. | ||
* If `nextFrame` is `_FutureImpl` then we can take the first `_FutureListener` in `listeners` and then the next frame is `(listener.callback, listener.result)`. | ||
* If `nextFrame` is `_AsyncStarStreamController` then we get `asyncStarStreamController.controller.subscription._onData`, which should give us an instance of `_StreamIterator`, which inside contains a `_FutureImpl` on which `await for` is waiting. | ||
|
||
Awaiter unwinding is implemented in by [`dart::StackTraceUtils::CollectFrames`] in [`runtime/vm/stack_trace.cc`]. | ||
|
||
### `@pragma('vm:awaiter-link')` | ||
|
||
Dart code which does not use `async`/`async*` functions and instead uses callbacks and lower-level primitives can integrate with awaiter frame unwinding by annotating variables which link to the next awaiter frame with `@pragma('vm:awaiter-link')`. | ||
|
||
Consider the following variation of the example: | ||
|
||
```dart | ||
Future<int> outer() { | ||
final completer = Completer<int>(); | ||
int process(int v) { | ||
completer.complete(v); | ||
} | ||
inner().then(v); | ||
return completer.future; | ||
} | ||
``` | ||
|
||
Running this would produce the following stack trace: | ||
|
||
``` | ||
#0 inner | ||
<asynchronous suspension> | ||
#1 outer.process | ||
<asynchronous suspension> | ||
``` | ||
|
||
Runtime is unable to unwind the awaiter stack past `process`. However if `completer` is annotated with `@pragma('vm:awaiter-link')` then unwinder will know where to continue: | ||
|
||
```dart | ||
Future<int> outer() { | ||
@pragma('vm:awaiter-link') | ||
final completer = Completer<int>(); | ||
// ... | ||
} | ||
``` | ||
|
||
``` | ||
#0 inner | ||
<asynchronous suspension> | ||
#1 outer.process | ||
<asynchronous suspension> | ||
#2 main | ||
<asynchronous suspension> | ||
``` | ||
|
||
`vm:awaiter-link` can be used in `dart:async` internals to avoid hardcoding recognition of specific methods into the runtime system, see for example `_SuspendState.thenCallback` or `Future.timeout` implementations. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.