a4e162f761
Inspector will no longer report per-function wasm scripts or provide wasm disassembly. Locations in wasm are now consistently reported through the inspector API as lineNumber=0 columnNumber=byte offset in module. Bug: chromium:1013527, chromium:1003022 Change-Id: Ide85bbaa85ad75f29248ff82a3e7f3e40688d377 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1991481 Commit-Queue: Eric Leese <leese@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#65660}
20 lines
924 B
Plaintext
20 lines
924 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":0,"columnNumber":55}
|
|
- [2] {"functionName":"main","lineNumber":0,"columnNumber":62}
|
|
- [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!
|