Files
v8/test/inspector/debugger/script-origin-stack-expected.txt
Paolo Severini 7a6c6f9ea6 [debug][wasm] Add support for 'build_id' custom section
Clang (and Emscripten) generate a unique build identifier,
stored in the 'build_id' custom section, as described in
https://github.com/WebAssembly/tool-conventions/issues/133.

This can be useful for DevTools to retrieve matching Wasm symbol
files from external symbol servers.

Bug: 381999814

Change-Id: Iec0690b8d44967f0470bf1a85e7d7b0031879ada
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6040773
Reviewed-by: Simon Zünd <szuend@chromium.org>
Reviewed-by: Clemens Backes <clemensb@chromium.org>
Commit-Queue: Paolo Severini <paolosev@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#97607}
2024-12-06 13:01:29 +00:00

37 lines
948 B
Plaintext

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