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}
13 lines
364 B
Plaintext
13 lines
364 B
Plaintext
Tests GC within DebugBreak
|
|
|
|
Running test: test
|
|
Script wasm://wasm/38e28046 byte offset 51: Wasm opcode 0x20 (kExprLocalGet)
|
|
GC triggered
|
|
Debugger.resume
|
|
Hello World (v8://test/instantiate:11:36)
|
|
at bar (v8://test/instantiate:11:36)
|
|
at $wasm_A (wasm://wasm/38e28046:1:54)
|
|
at test (test.js:4:20)
|
|
at (anonymous function) (:1:1)
|
|
exports.main returned!
|