b0c4f2b090
Wasm stack traces now show the url to the wasm script. Bug: v8:9762 Change-Id: Ie7feda499ec76bf001dea093efb720ffd691edad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2051946 Commit-Queue: Kim-Anh Tran <kimanh@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#66302}
20 lines
649 B
Plaintext
20 lines
649 B
Plaintext
Tests imports in wasm
|
|
Installing code and global variable.
|
|
Calling instantiate function for module A.
|
|
Waiting for wasm script to be parsed.
|
|
Got wasm script!
|
|
Setting breakpoint in line 1:
|
|
Script wasm://wasm/8c388106 byte offset 33: Wasm opcode 0x1
|
|
Calling instantiate function for module B.
|
|
Calling main function on module B.
|
|
Paused at 0:33.
|
|
Script wasm://wasm/8c388106 byte offset 33: Wasm opcode 0x1
|
|
Getting current stack trace via "new Error().stack".
|
|
Error
|
|
at v8://test/getStack:1:1
|
|
at func (<anonymous>:wasm-function[0]:0x21)
|
|
at main (<anonymous>:wasm-function[1]:0x2f)
|
|
at v8://test/runWasm:1:22
|
|
exports.main returned.
|
|
Finished.
|