[Lldb-commits] [lldb] [lldb] Add jLLDBSettings remote packet (PR #229179)

[Greg Clayton via lldb-commits]

================
@@ -284,6 +284,38 @@ the modules will be interesting to the client.
 will be used, which may be slower if the target contains a large number of modules
 and the communication link has a non-negligible latency.
 
+## jLLDBSettings
+
+This packet requests LLDB-specific settings for the process on the current
+GDB-remote connection. It requires the `lldb-settings+` feature from
+`qSupported`.
+
+```
+LLDB SENDS:    jLLDBSettings
+STUB REPLIES:  {"dyld_plugin_name":<string>,"accelerator_plugin_name":<string>,"send_dyld_packet_to_accelerator":<boolean>}
+```
+
+The fields are:
+
+- `dyld_plugin_name`: The name of the dynamic-loader plugin LLDB should use. If
+  absent or empty LLDB will select the dynamic loader based on the target
+  triple automatically.
+- `accelerator_plugin_name`: identifies the server-side accelerator plugin.
+  This setting is only needed when `send_dyld_packet_to_accelerator` is false.
+- `send_dyld_packet_to_accelerator`: if true, LLDB sends the dynamic-loader
+  packet on this accelerator connection. If false, LLDB sends it on the native
+  process's connection, which forwards it to `accelerator_plugin_name`. If
----------------
clayborg wrote:

Expand the comment a bit to explain why:
```
process's connection, which forwards it to `accelerator_plugin_name` which
will call a method in the LLDBServerAcceleratorPlugin::GetDynamicLoaderLibraryInfos. 
This allows an external GDB server to be spawned for the accelerator connection which
has not knowledge of shared libraries and allows the accelerator plug-in to use the 
CPU or accelerator connection to get the list of shared libraries.
```

https://github.com/llvm/llvm-project/pull/229179