v8/test/inspector/debugger/async-promise-late-then-expected.txt

Checks async stack for late .then handlers with gc
foo1 (test.js:11:2)
-- Promise.resolve --
test (test.js:20:2)
(anonymous) (expr.js:0:0)

foo1 (test.js:11:2)
-- Promise.resolve --
test (test.js:20:2)
(anonymous) (expr.js:0:0)

foo1 (test.js:11:2)
-- Promise.resolve --
test (test.js:20:2)
(anonymous) (expr.js:0:0)
[inspector] async stacks for Promise.then calls... ... which were done after the promise has been resolved. Goal of this CL - change promise instrumentation to support better callbacks, chained after promise resolution and prepare instrumentation for adding new asyncTaskCreated instrumentation. Instrumentation changes: - asyncTaskScheduled(recurring) when promise is fulfilled or rejected, - asyncTaskCancelled when promise is collected (since [1] we can be sure that promise will survive scheduled microtasks). Minor changes: - async task type in inspector <-> debugger API transferred by enum instead of string, - Debug manages async task ids based on promise objects. More details: https://docs.google.com/document/d/1u19N45f1gSF7M39mGsycJEK3IPyJgIXCBnWyiPeuJFE [1] https://codereview.chromium.org/2581503003/ BUG=chromium:632829,v8:5738 R=dgozman@chromium.org,yangguo@chromium.org,gsathya@chromium.org Review-Url: https://codereview.chromium.org/2578923002 Cr-Commit-Position: refs/heads/master@{#42178} 2017-01-10 12:54:12 +00:00			`Checks async stack for late .then handlers with gc`
			`foo1 (test.js:11:2)`
			`-- Promise.resolve --`
			`test (test.js:20:2)`
			`(anonymous) (expr.js:0:0)`

			`foo1 (test.js:11:2)`
			`-- Promise.resolve --`
			`test (test.js:20:2)`
			`(anonymous) (expr.js:0:0)`

			`foo1 (test.js:11:2)`
			`-- Promise.resolve --`
			`test (test.js:20:2)`
			`(anonymous) (expr.js:0:0)`