v8/test/inspector/debugger/get-possible-breakpoints-lazy-error-expected.txt
Philip Pfaffe e71d328fb3 Report additional wasm script info on the CDP
Add a scriptLanguage enum to the new scripts events. This overhauls
crrev.com/c/2011083 that was related. Report the code section offset
as well as the script language on the Debugger.scriptParsed and
Debugger.scriptFailedToParse events.

Bug: chromium:1057569
Change-Id: I40b43f28f0b3e094720db4fc1f07db1a0c293ee0
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083025
Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Reviewed-by: Clemens Backes <clemensb@chromium.org>
Commit-Queue: Philip Pfaffe <pfaffe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66749}
2020-03-17 13:25:24 +00:00

27 lines
608 B
Plaintext

getPossibleBreakpoints should not crash during lazy compilation (crbug.com/715334)
{
method : Debugger.scriptFailedToParse
params : {
endColumn : 23
endLine : 2
executionContextId : <executionContextId>
hasSourceURL : true
hash : 1bce5d0c4da4d13a3ea6e6f35ea0f34705c26ba4
isModule : false
length : 56
scriptId : <scriptId>
scriptLanguage : JavaScript
sourceMapURL :
startColumn : 0
startLine : 0
url : test.js
}
}
{
id : <messageId>
result : {
locations : [
]
}
}