Lines Matching refs:remote

7 process will be the remote system.
9 To enable remote debugging, LLDB employs a client-server architecture. The
10 client part runs on the local system and the remote system runs the server. The
11 client and server communicate using the gdb-remote protocol, usually
13 the LLDB-specific extensions are documented in docs/lldb-gdb-remote.txt file
14 inside LLDB source repository. Besides the gdb-remote stub, the server part of
16 advanced debugging operations, like copying files from/to the remote system and
17 can be used to execute arbitrary shell commands on the remote system.
19 In order to reduce code complexity and improve remote debugging experience LLDB
20 on Linux and macOS uses the remote debugging stub even when debugging a process
21 locally. This is achieved by spawning a remote stub process locally and
33 expressions) is same as in the local case, in the case of remote debugging,
35 remote system automatically. Also, if the remote system runs a different OS or
41 On Linux and Android, all required remote functionality is contained in the
43 gdb-remote stub. A single binary facilitates deployment and reduces code size,
47 lldb. On macOS and iOS, the remote-gdb functionality is implemented by the
50 The binaries mentioned above need to be present on the remote system to enable
51 remote debugging. You can either compile on the remote system directly or copy
52 them from the local machine. If compiling locally and the remote architecture
63    remote% lldb-server platform --listen "*:1234" --server
74 On the local system, you need to let LLDB know that you intend to do remote
76 As a first step you need to choose the correct platform plug-in for your remote
85    remote-freebsd: Remote FreeBSD user platform plug-in.
86    remote-linux: Remote Linux user platform plug-in.
87    remote-netbsd: Remote NetBSD user platform plug-in.
88    remote-windows: Remote Windows user platform plug-in.
89    remote-android: Remote Android user platform plug-in.
90    remote-ios: Remote iOS platform plug-in.
91    remote-macosx: Remote macOS user platform plug-in.
96    remote-tvos: Remote Apple TV platform plug-in.
97    remote-watchos: Remote Apple Watch platform plug-in.
98    remote-gdb-server: A platform that uses the GDB remote protocol as the communication transport.
102 different kinds of systems. The remote plug-ins are prefixed with "remote-".
103 For example, to debug a remote Linux application:
107    (lldb) platform select remote-linux
111 because remote plug-ins need to be connected to their remote platform
119    (lldb) platform connect connect://remote:1234
120      Platform: remote-linux
122      Hostname: remote
131 attach to attach to an existing remote process or target create, process launch
138 Launching a locally built process on the remote machine
144 To launch a locally built process on the remote system in the platform working
176      Platform: remote-linux
178      Hostname: remote
184 Install and run by specifying a remote install path
199 uploaded to the remote system by default when launching the application. If you
213 Attaching to a remote process
216 If you want to attach to a remote process, you can first list the processes on
217 the remote system:
222    223 matching processes were found on "remote-linux"
228 Then attaching is as simple as specifying the remote process ID: