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}
20 lines
922 B
Plaintext
20 lines
922 B
Plaintext
Tests call stack in wasm scripts
|
|
Running testFunction with generated wasm bytes...
|
|
Paused on 'debugger;'
|
|
Number of frames: 5
|
|
- [0] {"functionName":"call_debugger","function_lineNumber":1,"function_columnNumber":24,"lineNumber":2,"columnNumber":4}
|
|
- [1] {"functionName":"call_func","lineNumber":1,"columnNumber":2}
|
|
- [2] {"functionName":"main","lineNumber":2,"columnNumber":4}
|
|
- [3] {"functionName":"testFunction","function_lineNumber":0,"function_columnNumber":21,"lineNumber":14,"columnNumber":19}
|
|
- [4] {"functionName":"","function_lineNumber":0,"function_columnNumber":0,"lineNumber":0,"columnNumber":0}
|
|
Getting v8-generated stack trace...
|
|
Result of evaluate (string):
|
|
Error: this is your stack trace:
|
|
-- skipped --
|
|
at call_debugger (<anonymous>:3:5)
|
|
at call_func (wasm-function[1]:0x37)
|
|
at main (wasm-function[2]:0x3e)
|
|
at testFunction (<anonymous>:15:20)
|
|
at <anonymous>:1:1
|
|
Finished!
|