From e960f1ec47c3e0060e3031432293c8a1c99381cb Mon Sep 17 00:00:00 2001 From: Max Desiatov Date: Tue, 21 Oct 2025 21:26:28 +0100 Subject: [PATCH] Refine `qWasmCallStack` documentation (#163803) `qWasmCallStack` documentation is not clear enough in how the list of PC values is delimited and the size of these values. --- lldb/docs/resources/lldbgdbremote.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/lldb/docs/resources/lldbgdbremote.md b/lldb/docs/resources/lldbgdbremote.md index 287484ea5cab..032edb66690e 100644 --- a/lldb/docs/resources/lldbgdbremote.md +++ b/lldb/docs/resources/lldbgdbremote.md @@ -2491,9 +2491,10 @@ The packet below are supported by the ### qWasmCallStack Get the Wasm call stack for the given thread id. This returns a hex-encoded -list of PC values, one for each frame of the call stack. To match the Wasm -specification, the addresses are encoded in little endian byte order, even if -the endian of the Wasm runtime's host is not little endian. +list (with no delimiters) of 64-bit PC values, one for each frame of the call +stack. To match the Wasm specification, the addresses are encoded in little +endian byte order, even if the endian of the Wasm runtime's host is not little +endian. ``` send packet: $qWasmCallStack:202dbe040#08