a4e162f761
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}
11 lines
260 B
Plaintext
11 lines
260 B
Plaintext
Tests how wasm scrips report the source
|
|
Check that inspector gets wasm bytecode
|
|
Paused on debugger!
|
|
Number of frames: 5
|
|
[0] debugger;
|
|
[1] Wasm offset 72: 0x10
|
|
[2] Wasm offset 81: 0x11
|
|
[3] instance.exports.main();
|
|
[4] testFunction(module_bytes)
|
|
Finished.
|