llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-lldb Author: Max Desiatov (MaxDesiatov) <details> <summary>Changes</summary> The current description mistakenly specified that an address of the local value in some address space is returned. When testing this with Wasm runtimes that already implement this command, it can be clearly seen that the value is returned. The value itself may be an address for languages that use shadow stack in Wasm linear memory, but the value of an arbitrary local does not always contain that address. --- Full diff: https://github.com/llvm/llvm-project/pull/170393.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 36b95f1073ebc..80e76fed8c78b 100644 --- a/lldb/docs/resources/lldbgdbremote.md +++ b/lldb/docs/resources/lldbgdbremote.md @@ -2505,7 +2505,7 @@ variables. Get the value of a Wasm function argument or local variable for the given frame index at the given variable index. The indexes are encoded as base 10. The -result is a hex-encoded address from where to read the value. +result is a hex-encoded little-endian value of the local. ``` `````````` </details> https://github.com/llvm/llvm-project/pull/170393 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
