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
39 lldb-server binary. This binary combines the functionality of the platform and
55 platform mode and specify the port it should listen on. For example, the
60 remote% lldb-server platform --listen "*:1234" --server
62 will start the LLDB platform and wait for incoming connections from any address
72 debugging. This is achieved through the platform command and its sub-commands.
73 As a first step you need to choose the correct platform plug-in for your remote
74 system. A list of available plug-ins can be obtained through platform list.
79 (lldb) platform list
81 host: Local macOS user platform plug-in.
82 remote-freebsd: Remote FreeBSD user platform plug-in.
83 remote-linux: Remote Linux user platform plug-in.
84 remote-netbsd: Remote NetBSD user platform plug-in.
85 remote-windows: Remote Windows user platform plug-in.
86 remote-android: Remote Android user platform plug-in.
87 remote-ios: Remote iOS platform plug-in.
88 remote-macosx: Remote macOS user platform plug-in.
89 ios-simulator: iOS simulator platform plug-in.
90 darwin-kernel: Darwin Kernel platform plug-in.
91 tvos-simulator: Apple TV simulator platform plug-in.
92 watchos-simulator: Apple Watch simulator platform plug-in.
93 remote-tvos: Remote Apple TV platform plug-in.
94 remote-watchos: Remote Apple Watch platform plug-in.
95 remote-gdb-server: A platform that uses the GDB remote protocol as the communication transport.
97 The default platform is the platform host which is used for local debugging.
104 (lldb) platform select remote-linux
106 After selecting the platform plug-in, you should receive a prompt which
107 confirms the selected platform, and states that you are not connected. This is
108 because remote plug-ins need to be connected to their remote platform
109 counterpart to operate. This is achieved using the platform connect command.
116 (lldb) platform connect connect://remote:1234
117 Platform: remote-linux
123 Note that the platform has a working directory of /tmp. This directory will be
129 to start a new one. The platform plugin will transparently take care of
131 application needs additional files, you can transfer them using the platform
133 further using the platform shell command.
135 When using the "remote-android" platform, the client LLDB forwards two ports, one
136 for connecting to the platform, and another for connecting to the gdbserver.
143 Install and run in the platform working directory
146 To launch a locally built process on the remote system in the platform working
156 platform's current working directory only if the file has changed. The platform
163 Changing the platform working directory
166 You can change the platform working directory while connected to the platform
171 (lldb) platform settings -w /usr/local/bin
173 And you can verify it worked using "platform status":
177 (lldb) platform status
178 Platform: remote-linux
190 the platform's current working directory, we can set the platform file
200 instead of the platform current working directory. Only the main executable is
203 locally build shared library to the current target and set its platform file
223 (lldb) platform process list