AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
459283200c
v8/test/inspector/debugger/continue-to-location-target-call-frames-expected.txt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

82 lines
1.4 KiB
Plaintext
Raw Normal View History

[inspector] added targetCallFrames for continueToLocation By default we just break when we first time reach passed location, with current - we'll break at passed location only when it happens within the same stack frame. BUG=v8:6397 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2879923003 Cr-Commit-Position: refs/heads/master@{#45354}
2017-05-16 21:52:49 +00:00
Check that continue-to-location works with different strategies.
Running test: testAwaitAny
(anonymous) (expr.js:0:0)
asyncFact (test.js:9:2)
(anonymous) (expr.js:0:0)
asyncFact (test.js:11:2)
-- async function --
[inspector] reworked async stack instrumentation for async functions New intstrumentation consists of: - kAsyncFunctionSuspended when async function is suspended on await (called on each await), - kAsyncFunctionFinished when async function is finished. Old instrumentation was based on reusing async function promise. Using this promise produces couple side effects: - for any promise instrumentation we first need to check if it is special case for async function promise or not - it requires expensive reading from promise object. - we capture stack for async functions even if it does not contain awaits. - we do not properly cancel async task created for async function. New intsrumntation resolved all these problems as well as provide clear mapping between async task and generator which we can use later to fetch scope information for async functions on pause. R=dgozman@chromium.org,yangguo@chromium.org Bug: v8:7078 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ifdcec947d91e6e3d4d5f9029bc080a19b8e23d41 Reviewed-on: https://chromium-review.googlesource.com/1043096 Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#53445}
2018-05-30 14:21:39 +00:00
asyncFact (test.js:10:20)
[inspector] added targetCallFrames for continueToLocation By default we just break when we first time reach passed location, with current - we'll break at passed location only when it happens within the same stack frame. BUG=v8:6397 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2879923003 Cr-Commit-Position: refs/heads/master@{#45354}
2017-05-16 21:52:49 +00:00
asyncFact (test.js:10:20)
asyncFact (test.js:10:20)
asyncFact (test.js:10:20)
(anonymous) (expr.js:0:0)
Running test: testAwaitCurrent
(anonymous) (expr.js:0:0)
asyncFact (test.js:9:2)
(anonymous) (expr.js:0:0)
asyncFact (test.js:11:2)
-- async function --
[inspector] reworked async stack instrumentation for async functions New intstrumentation consists of: - kAsyncFunctionSuspended when async function is suspended on await (called on each await), - kAsyncFunctionFinished when async function is finished. Old instrumentation was based on reusing async function promise. Using this promise produces couple side effects: - for any promise instrumentation we first need to check if it is special case for async function promise or not - it requires expensive reading from promise object. - we capture stack for async functions even if it does not contain awaits. - we do not properly cancel async task created for async function. New intsrumntation resolved all these problems as well as provide clear mapping between async task and generator which we can use later to fetch scope information for async functions on pause. R=dgozman@chromium.org,yangguo@chromium.org Bug: v8:7078 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ifdcec947d91e6e3d4d5f9029bc080a19b8e23d41 Reviewed-on: https://chromium-review.googlesource.com/1043096 Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#53445}
2018-05-30 14:21:39 +00:00
asyncFact (test.js:10:20)
[inspector] added targetCallFrames for continueToLocation By default we just break when we first time reach passed location, with current - we'll break at passed location only when it happens within the same stack frame. BUG=v8:6397 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2879923003 Cr-Commit-Position: refs/heads/master@{#45354}
2017-05-16 21:52:49 +00:00
(anonymous) (expr.js:0:0)
Running test: testAny
(anonymous) (expr.js:0:0)
fact (test.js:16:2)
(anonymous) (expr.js:0:0)
fact (test.js:18:2)
fact (test.js:17:14)
fact (test.js:17:14)
fact (test.js:17:14)
(anonymous) (expr.js:0:0)
Running test: testCurrent
(anonymous) (expr.js:0:0)
fact (test.js:16:2)
(anonymous) (expr.js:0:0)
fact (test.js:18:2)
(anonymous) (expr.js:0:0)
Running test: testTopLevelAny
(anonymous) (expr.js:0:0)
topLevel (test.js:23:2)
(anonymous) (expr.js:0:0)
(anonymous) (:1:10)
topLevel (test.js:23:2)
(anonymous) (expr.js:0:0)
(anonymous) (:4:10)
topLevel (test.js:23:2)
(anonymous) (expr.js:0:0)
Running test: testTopLevelCurrent
(anonymous) (expr.js:0:0)
topLevel (test.js:23:2)
(anonymous) (expr.js:0:0)
(anonymous) (:1:10)
topLevel (test.js:23:2)
(anonymous) (expr.js:0:0)
(anonymous) (:4:10)
topLevel (test.js:23:2)
(anonymous) (expr.js:0:0)
Reference in New Issue Copy Permalink