Lines Matching full:platform
15 LLDB also consists of a platform binary, which is responsible for performing
23 debugging this whole process is transparent to the user. The platform binary is
42 lldb-server binary. This binary combines the functionality of the platform and
58 platform mode and specify the port it should listen on. For example, the
63 remote% lldb-server platform --listen "*:1234" --server
65 will start the LLDB platform and wait for incoming connections from any address
75 debugging. This is achieved through the platform command and its sub-commands.
76 As a first step you need to choose the correct platform plug-in for your remote
77 system. A list of available plug-ins can be obtained through platform list.
82 (lldb) platform list
84 host: Local macOS user platform plug-in.
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.
92 ios-simulator: iOS simulator platform plug-in.
93 darwin-kernel: Darwin Kernel platform plug-in.
94 tvos-simulator: Apple TV simulator platform plug-in.
95 watchos-simulator: Apple Watch simulator 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.
100 The default platform is the platform host which is used for local debugging.
107 (lldb) platform select remote-linux
109 After selecting the platform plug-in, you should receive a prompt which
110 confirms the selected platform, and states that you are not connected. This is
111 because remote plug-ins need to be connected to their remote platform
112 counterpart to operate. This is achieved using the platform connect command.
119 (lldb) platform connect connect://remote:1234
120 Platform: remote-linux
126 Note that the platform has a working directory of /tmp. This directory will be
132 to start a new one. The platform plugin will transparently take care of
134 application needs additional files, you can transfer them using the platform
136 further using the platform shell command.
138 When using the "remote-android" platform, the client LLDB forwards two ports, one
139 for connecting to the platform, and another for connecting to the gdbserver.
146 Install and run in the platform working directory
149 To launch a locally built process on the remote system in the platform working
159 platform's current working directory only if the file has changed. The platform
166 Changing the platform working directory
169 You can change the platform working directory while connected to the platform
174 (lldb) platform settings -w /usr/local/bin
176 And you can verify it worked using "platform status":
180 (lldb) platform status
181 Platform: remote-linux
193 the platform's current working directory, we can set the platform file
203 instead of the platform current working directory. Only the main executable is
206 locally build shared library to the current target and set its platform file
226 (lldb) platform process list