gdbserver

Start debug server

$ gdbserver :[port] [program]

$ gdbserver --attach :[port] [pid]

$ gdbserver --multi :[port]

$ gdbserver :[port] [program] [arg1] [arg2]

gdbserver comm [program] [args...]

gdbserver is a lightweight remote debugging stub that runs on the target system, allowing a full GDB debugger running on a different machine to control and debug programs remotely. This architecture is essential for embedded development, cross-compilation workflows, and debugging on resource-constrained devices.
The server component runs on the target system (embedded device, remote server, or different architecture), while the full GDB client runs on the developer's workstation. Communication occurs over TCP/IP or serial connections, with gdbserver translating GDB's debugging protocol into system-level debugging operations.
This split architecture minimizes the footprint on the target system, as gdbserver is much smaller than full GDB and requires fewer dependencies. It's particularly valuable for embedded Linux systems, IoT devices, and scenarios where the target lacks sufficient resources for a complete debugging environment.
Typical workflows involve starting gdbserver on the target with the program to debug, then connecting from a GDB client using commands like "target remote host:port". The full power of GDB is available remotely, including breakpoints, single-stepping, memory inspection, and core file generation.

COMM

Connection: :port or host:port.

Program to debug.

Attach to running process.

Multi-process mode.

Exit after client disconnects.

Enable debug output.

Display help information.

Requires network access to target. Security of debug connection. Target needs gdbserver installed.

gdbserver is part of GDB (GNU Debugger), enabling remote debugging scenarios since GDB 4.x. It's essential for embedded development and cross-platform debugging.

gdb(1), gdbinit(5)