b50dea24b1
Currently, when debugging wasm, the internal script URL is shown, which has the form wasm://wasm/wasm-<hex-script-id>. With this change, if the module specifies a module name, it would report the URL as wasm://wasm/<module-name>-<hex-script-id>, as this will help the user identify what they are debugging. Bug: chromium:1017678 Change-Id: I26ff6249bd1e832d62402619a68b61c115c24640 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1888810 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#64703}
14 lines
468 B
Plaintext
14 lines
468 B
Plaintext
Tests how wasm scripts are reported with name
|
|
Check that each inspector gets two wasm scripts at module creation time.
|
|
Session #1: Script #0 parsed. URL: wasm://wasm/49a8663e/49a8663e-0.
|
|
Session #1: Script #1 parsed. URL: wasm://wasm/moduleName-aea4a206/moduleName-aea4a206-0.
|
|
Session #1: Source for wasm://wasm/49a8663e/49a8663e-0:
|
|
func $nopFunction
|
|
nop
|
|
end
|
|
|
|
Session #1: Source for wasm://wasm/moduleName-aea4a206/moduleName-aea4a206-0:
|
|
func $nopFunction
|
|
nop
|
|
end
|