v8/test/inspector/debugger/script-origin-stack-expected.txt
Alexey Kozyatinskiy b2b7e8deb4 inspector: do not report async tail in Debugger.scriptParsed event
Async tail might be long. On frontend side we use only top frame so
we can report tail using id.

R=dgozman@chromium.org

Bug: chromium:873865
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ie9e6b5c4c000cc6bedce2d5fec9f3fa22ea21768
Reviewed-on: https://chromium-review.googlesource.com/c/1286959
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56784}
2018-10-18 16:16:57 +00:00

34 lines
855 B
Plaintext

Debugger.scriptParsed.stackTrace should contain only one frame
{
method : Debugger.scriptParsed
params : {
endColumn : 0
endLine : 0
executionContextId : <executionContextId>
hasSourceURL : false
hash : 3fb75160ab1f4e4e82675bc4cd924d3481abe278
isLiveEdit : false
isModule : false
length : 0
scriptId : <scriptId>
sourceMapURL :
stackTrace : {
callFrames : [
[0] : {
columnNumber : 17
functionName : setTimeout
lineNumber : 0
scriptId : <scriptId>
url :
}
]
parentId : {
id : <id>
}
}
startColumn : 0
startLine : 0
url :
}
}