v8/test/inspector/debugger/wasm-stepping-in-from-js-expected.txt
Eric Leese a4e162f761 Remove fake wasm scripts from V8 backend
Inspector will no longer report per-function wasm scripts or
provide wasm disassembly. Locations in wasm are now consistently
reported through the inspector API as lineNumber=0
columnNumber=byte offset in module.

Bug: chromium:1013527, chromium:1003022
Change-Id: Ide85bbaa85ad75f29248ff82a3e7f3e40688d377
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1991481
Commit-Queue: Eric Leese <leese@chromium.org>
Reviewed-by: Clemens Backes <clemensb@chromium.org>
Reviewed-by: Simon Zünd <szuend@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#65660}
2020-01-09 13:21:01 +00:00

33 lines
708 B
Plaintext

Tests stepping from javascript into wasm
Installing code and global variable.
Calling instantiate function.
Waiting for wasm scripts to be parsed.
Ignoring script with url v8://test/callInstantiate
Got wasm script: wasm://wasm/fa045c1e
Setting breakpoint on line 3 of wasm function
{
columnNumber : 37
lineNumber : 0
scriptId : <scriptId>
}
paused
function test() {
#debugger;
instance.exports.main(1);
Debugger.stepInto
paused
debugger;
#instance.exports.main(1);
}
Debugger.stepInto
paused
Script wasm://wasm/fa045c1e byte offset 35: Wasm opcode 0x20
Debugger.resume
paused
Script wasm://wasm/fa045c1e byte offset 37: Wasm opcode 0x41
Debugger.resume
exports.main returned!
Finished!