v8/test/inspector/debugger/set-async-call-stack-depth-expected.txt
kozyatinskiy f61facfdaf [inspector] use creation stack trace as parent for async call chains
Creation stack trace points to the place where callback was actually chained, scheduled points where parent promise was resolved.
For async tasks without creation stack (e.g. setTimeout) we continue to use scheduled as creation since usually they are the same.

BUG=v8:6189
R=dgozman@chromium.org

Review-Url: https://codereview.chromium.org/2868493002
Cr-Original-Commit-Position: refs/heads/master@{#45198}
Committed: e118462f18
Review-Url: https://codereview.chromium.org/2868493002
Cr-Commit-Position: refs/heads/master@{#45266}
2017-05-11 19:21:24 +00:00

38 lines
734 B
Plaintext

Checks that we report not more then maxDepth call chains.
Running test: testPaused
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 16
reported: 1
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 8
reported: 1
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 7
reported: 1
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 0
reported: 0
Running test: testConsoleTrace
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 16
reported: 1
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 8
reported: 1
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 7
reported: 1
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 0
reported: 0