9face69066
This changes the names reported in stack traces via the Chrome DevTools protocol to follow the WAT naming convention for functions. This aligns the behavior here with the rest of DevTools (i.e. the disassembly in the Sources panel and the Scope sidebar, as well as the Console REPL) to use one consistent naming scheme. Fixed: chromium:1159307 Doc: http://bit.ly/devtools-wasm-entities Bug: chromium:1162229, chromium:1164241, chromium:1071432 Change-Id: Ibe543f39c775944072073fe5f0959412529aa19b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2878734 Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#74456}
20 lines
950 B
Plaintext
20 lines
950 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 (<anonymous>:wasm-function[1]:0x37)
|
|
at main (<anonymous>:wasm-function[2]:0x3e)
|
|
at testFunction (<anonymous>:15:20)
|
|
at <anonymous>:1:1
|
|
Finished!
|