v8/test/inspector/debugger/wasm-gc-breakpoints-expected.txt
Benedikt Meurer 9face69066 [inspector] Use consistent names for Wasm functions.
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}
2021-05-10 06:30:21 +00:00

32 lines
876 B
Plaintext

Tests GC object inspection.
Running test: test
Instantiating.
Waiting for wasm script (ignoring first non-wasm script).
Setting breakpoint at offset 107 on script wasm://wasm/22e4830a
Calling main()
Paused:
Script wasm://wasm/22e4830a byte offset 107: Wasm opcode 0x21 (kExprLocalSet)
Scope:
at $main (0:107):
- scope (wasm-expression-stack):
0: Array ((ref $ArrC))
object details:
0: Struct ((ref null $StrA))
length: 1 (number)
- scope (local):
$varA: Struct ((ref null $StrA))
$varB: null ((ref null $ArrC))
object details:
$byte: 127 (i8)
$word: 32767 (i16)
$pointer: Struct ((ref $StrB))
- scope (module):
instance: exports: "main" (Function)
module: Module
functions: "$main": (Function)
globals: "$global0": function 0() { [native code] } ((ref null $type3))
at (anonymous) (0:17):
-- skipped
exports.main returned!