[Lldb-commits] [lldb] [lldb][docs] Some fixes for lldbgdbremote.md. (PR #200079)
David Spickett via lldb-commits
lldb-commits at lists.llvm.org
Thu May 28 02:17:28 PDT 2026
================
@@ -1312,7 +1312,7 @@ some key value pairs. The key value pairs in the command are:
be listed for all users, not just the user that the
platform is running as
* `triple` - `string` -
- An ASCII triple string (`x86_64`, `x86_64-apple-macosx`, `armv7-apple-ios`)
+ An hex encoded triple string (hex encodings of `x86_64`, `x86_64-apple-macosx`, `armv7-apple-ios`)
----------------
DavidSpickett wrote:
I am confused because the code implies that it's a normal string.
In GDBRemoteCommunicationClient::FindProcesses:
```
if (match_info.GetProcessInfo().GetArchitecture().IsValid()) {
const ArchSpec &match_arch =
match_info.GetProcessInfo().GetArchitecture();
const llvm::Triple &triple = match_arch.GetTriple();
packet.PutCString("triple:");
packet.PutCString(triple.getTriple());
packet.PutChar(';');
}
```
The server also thinks it's a normal string:
```
} else if (key == "triple") {
match_info.GetProcessInfo().GetArchitecture() =
HostInfo::GetAugmentedArchSpec(value);
} else {
```
However, I do see it hex encoded in the logs when I get a **response**:
```
lldb < 17> send packet: $qfProcessInfo#42
lldb < 219> read packet: $pid:1427;ppid:1;uid:24900;gid:24900;euid:24900;egid:24900;name:2f75
73722f6c69622f73797374656d642f73797374656d64;args:2f6c69622f73797374656d642f73797374656d64-2d2d75736572;t
riple:616172636836342d2d6c696e75782d676e75;#ea
```
To be sending a triple to the server I think I need to use:
```
(lldb) platform process list --arch arm64
error: invalid combination of options for the given command
```
But it doesn't actually work.
https://github.com/llvm/llvm-project/pull/200079
More information about the lldb-commits
mailing list