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}
44 lines
884 B
Plaintext
44 lines
884 B
Plaintext
Checks that async stacks works for async/await
|
|
foo2 (test.js:15:2)
|
|
-- async function (test.js:13:19)--
|
|
foo2 (test.js:13:19)
|
|
test (test.js:24:8)
|
|
(anonymous) (expr.js:0:0)
|
|
|
|
foo2 (test.js:17:2)
|
|
-- async function (test.js:13:19)--
|
|
foo2 (test.js:13:19)
|
|
test (test.js:24:8)
|
|
(anonymous) (expr.js:0:0)
|
|
|
|
foo1 (test.js:9:2)
|
|
foo2 (test.js:18:8)
|
|
-- async function (test.js:13:19)--
|
|
foo2 (test.js:13:19)
|
|
test (test.js:24:8)
|
|
(anonymous) (expr.js:0:0)
|
|
|
|
foo1 (test.js:9:2)
|
|
-- Promise.resolve (test.js:19:43)--
|
|
-- Promise.resolve (test.js:19:16)--
|
|
foo2 (test.js:19:30)
|
|
-- async function (test.js:13:19)--
|
|
foo2 (test.js:13:19)
|
|
test (test.js:24:8)
|
|
(anonymous) (expr.js:0:0)
|
|
|
|
foo2 (test.js:20:2)
|
|
-- async function (test.js:13:19)--
|
|
foo2 (test.js:13:19)
|
|
test (test.js:24:8)
|
|
(anonymous) (expr.js:0:0)
|
|
|
|
{
|
|
id : <messageId>
|
|
result : {
|
|
result : {
|
|
type : undefined
|
|
}
|
|
}
|
|
}
|