llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-lldb Author: Max Desiatov (MaxDesiatov) <details> <summary>Changes</summary> `qWasmCallStack` is not clear if the list of PC values is delimited and the size of these values. --- Full diff: https://github.com/llvm/llvm-project/pull/163803.diff 1 Files Affected: - (modified) lldb/docs/resources/lldbgdbremote.md (+1-1) ``````````diff 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. `````````` </details> https://github.com/llvm/llvm-project/pull/163803 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
