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}
8 lines
346 B
Plaintext
8 lines
346 B
Plaintext
Tests how wasm scripts are reported with name
|
|
Check that the inspector gets four wasm scripts at module creation time.
|
|
Session #1: Script #0 parsed. URL: wasm://wasm/49a8663e.
|
|
Session #1: Script #1 parsed. URL: wasm://wasm/moduleName-aea4a206.
|
|
Session #1: Source for wasm://wasm/49a8663e:
|
|
|
|
Session #1: Source for wasm://wasm/moduleName-aea4a206:
|