a1d2e34260
This is a minor cosmetic fix. Wasm opcodes are bytes, hence they should always be printed as an even number of hexadecimal digits. Note that currently we only print a single byte anyway, but in the future we will want to extend this to correctly parse multi-byte opcodes. Those will also be printed as an even number of characters then. R=thibaudm@chromium.org Bug: v8:10351 Change-Id: I2423277b470d74c1c72cb619c2a43bb978423bc0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2122025 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66883}
20 lines
651 B
Plaintext
20 lines
651 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 0x01
|
|
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 0x01
|
|
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.
|