Skip to content

Commit 4e0f4eb

Browse files
MaxDesiatovaokblast
authored andcommitted
Refine qWasmCallStack documentation (llvm#163803)
`qWasmCallStack` documentation is not clear enough in how the list of PC values is delimited and the size of these values.
1 parent e2f0a77 commit 4e0f4eb

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

lldb/docs/resources/lldbgdbremote.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2491,9 +2491,10 @@ The packet below are supported by the
24912491
### qWasmCallStack
24922492
24932493
Get the Wasm call stack for the given thread id. This returns a hex-encoded
2494-
list of PC values, one for each frame of the call stack. To match the Wasm
2495-
specification, the addresses are encoded in little endian byte order, even if
2496-
the endian of the Wasm runtime's host is not little endian.
2494+
list (with no delimiters) of 64-bit PC values, one for each frame of the call
2495+
stack. To match the Wasm specification, the addresses are encoded in little
2496+
endian byte order, even if the endian of the Wasm runtime's host is not little
2497+
endian.
24972498
24982499
```
24992500
send packet: $qWasmCallStack:202dbe040#08

0 commit comments

Comments
 (0)