https://github.com/MaxDesiatov created https://github.com/llvm/llvm-project/pull/163803
`qWasmCallStack` is not clear if the list of PC values is delimited and the size of these values. >From 2d50565e6ad91edc4700484e183fb974d3281cdb Mon Sep 17 00:00:00 2001 From: Max Desiatov <[email protected]> Date: Thu, 16 Oct 2025 15:57:25 +0100 Subject: [PATCH] Refine `qWasmCallStack` documentation formatting `qWasmCallStack` is not clear if the list of PC values is delimited and the size of these values. --- lldb/docs/resources/lldbgdbremote.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lldb/docs/resources/lldbgdbremote.md b/lldb/docs/resources/lldbgdbremote.md index f0c5e6b04d54c..e529ef48f1ce0 100644 --- a/lldb/docs/resources/lldbgdbremote.md +++ b/lldb/docs/resources/lldbgdbremote.md @@ -2491,7 +2491,7 @@ 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 +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. _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
