b98dd0af92
With creation frame we can show additional information with description of each async stack trace, which could help user to understand where promises were chained. At least in case of Promise.resolve().then(foo1).then(foo2) we would be able to show following stack trace for break in foo2 callback: foo2 (test.js:14:2) -- Promise.resolve (test.js:29:14)-- -- Promise.resolve (test.js:28:14)-- promiseThen (test.js:30:2) More details: https://docs.google.com/document/d/1u19N45f1gSF7M39mGsycJEK3IPyJgIXCBnWyiPeuJFE BUG=v8:5738 R=dgozman@chromium.org,gsathya@chromium.org Review-Url: https://codereview.chromium.org/2648873002 Cr-Commit-Position: refs/heads/master@{#42682}
42 lines
1.1 KiB
JavaScript
42 lines
1.1 KiB
JavaScript
// Copyright 2016 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
print('Checks that async stacks works for async/await');
|
|
|
|
InspectorTest.addScript(`
|
|
async function foo1() {
|
|
debugger;
|
|
return Promise.resolve();
|
|
}
|
|
|
|
async function foo2() {
|
|
await Promise.resolve();
|
|
debugger;
|
|
await Promise.resolve();
|
|
debugger;
|
|
await foo1();
|
|
await Promise.all([ Promise.resolve() ]).then(foo1);
|
|
debugger;
|
|
}
|
|
|
|
async function test() {
|
|
await foo2();
|
|
}
|
|
//# sourceURL=test.js`, 7, 26);
|
|
|
|
InspectorTest.setupScriptMap();
|
|
Protocol.Debugger.onPaused(message => {
|
|
InspectorTest.logCallFrames(message.params.callFrames);
|
|
InspectorTest.logAsyncStackTrace(message.params.asyncStackTrace);
|
|
InspectorTest.log('');
|
|
Protocol.Debugger.resume();
|
|
});
|
|
|
|
Protocol.Debugger.enable();
|
|
Protocol.Debugger.setAsyncCallStackDepth({ maxDepth: 128 });
|
|
Protocol.Runtime.evaluate({ expression: 'test()//# sourceURL=expr.js',
|
|
awaitPromise: true })
|
|
.then(InspectorTest.logMessage)
|
|
.then(InspectorTest.completeTest);
|