beaf1073bd
Currently, in wasm-function stack traces, v8 displays the decimal offset from the start of the function. However, the WebAssembly WebAPI specification says that it should be a hex offset into the module. This change makes the stack trace display with hex module offsets, as well as fixing all the unit tests that depended on the old behaviour. R=fgm@chromium.org, titzer@chromium.org, yangguo@chromium.org Bug: v8:9172 Change-Id: I73737a319a42dd665521ab8a4b825199ae11c87f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1646846 Reviewed-by: Ben Titzer <titzer@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Commit-Queue: Guanzhong Chen <gzchen@google.com> Cr-Commit-Position: refs/heads/master@{#62103}
26 lines
550 B
Plaintext
26 lines
550 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:
|
|
func $func
|
|
#nop
|
|
end
|
|
|
|
Calling instantiate function for module B.
|
|
Calling main function on module B.
|
|
Paused at 1:2.
|
|
func $func
|
|
#nop
|
|
end
|
|
|
|
Getting current stack trace via "new Error().stack".
|
|
Error
|
|
at v8://test/getStack:1:1
|
|
at func (wasm-function[0]:0x21)
|
|
at main (wasm-function[1]:0x2f)
|
|
at v8://test/runWasm:1:22
|
|
exports.main returned.
|
|
Finished.
|