Debug remotely with GDB

When debugging on a target supported by GDB server, a local GDB process talks to a GDB server running on the remote machine that controls the process to be debugged.

The GDB server process is started on the remote machines by passing a port number and the executable:

gdbserver :1234 <executable>

It then typically responds:

Process bin/qtcreator created; pid = 5159
Listening on port 1234

On the local machine that runs Qt Creator:

1. Go to Debug > Start Debugging > Attach to Running Debug Server.

   

2. In Kit, select the build and run kit to use for building the project.
3. In Server port, enter the name of the remote machine and the port number to use.
4. In Local executable, specify the path to the application executable on the local machine.
5. In Command line arguments, specify command line arguments to be passed to the executable.
6. In Working directory, specify the working directory. It defaults to the directory of the build result.
7. Select Run in terminal for console applications.
8. Select Break at "main" to stop the debugger at the main function.
9. Select Use target extended-remote to connect to create the connection in the target extended-remote mode. In this mode, when the debugged application exits or you detach from it, the debugger remains connected to the target. You can rerun the application, attach to a running application, or use monitor commands specific to the target. For example, GDB does not exit unless it was invoked using the --once option, but you can make it exit by using the monitor exit command.
10. In Override SysRoot, specify the path to the sysroot to use instead of the default sysroot.
11. In Init commands, enter the commands to execute immediately after the connection to a target has been established.
12. In Reset commands, enter the commands to execute when resetting the connection to a target.
13. In Debug information, specify the location for storing debug information. You cannot use an empty path.
14. In Override server channel, specify a communication channel to use, such as a serial line or custom port.
15. In Recent, select a recent configuration to use.
16. Select OK to start debugging.

By default, a non-responsive GDB process is terminated after 40 seconds. To increase the timeout in GDB timeout, go to Preferences > Debugger > GDB.

For more information about connecting with target extended-remote mode in GDB, see Debugging with GDB: Connecting to a Remote Target.