Specify the arguments that will be passed to gdbserver: connection port, executable path, and additional arguments if required.īy default, this field contains the port you provided in 'target remote' args and the path from Upload path followed by the binary name.īy default for CMake projects, this configuration builds your target using the currently selected CMake profile and takes the binary from the Build directory folder. The default path is filled up automatically. Set the location of gdbserver on the remote machine. See gdb documentation for more details on connecting to a remote target. Provide the medium to carry debugging packets (serial line or an IP network using TCP or UDP). Specify the remote folder where the executable will be placed. You can also choose to skip uploading ( None). Your executable can be uploaded every time you start a debug session ( Always) or upon the changes in the binary ( Updated Only). You can also manage SSH configurations in Settings | Tools | SSH Configurations. Provide the credentials for accessing your remote machine: Select one of the existing SSH configurations from the drop-down list or click to create a new one.
Select the client debugger: bundled multiarch GDB (default), one of the toolchain debuggers, or a custom GDB binary. Select the target to be built ( CMake, Makefile, or custom target) and the executable to be uploaded remotely.Ĭlick the button to configure custom targets in the Settings | Build, Execution, Deployment | Custom Build Targets dialog. Go to Run | Edit Configurations, click, and select Remote GDB Server from the list of templates. The Remote GDB Server configuration builds your target locally, uploads the binary to the remote machine, launches it under gdbserver, and connects the CLion debugger.
0 kommentar(er)
