A GDB server bridges GDB and the hardware debug probe. GDB sends requests using its remote serial protocol; the server translates them into probe-specific operations for the target’s JTAG or SWD interface. section 6.5.2
The debugging path runs from GDB on the host, through the server and probe, to the target MCU. The server handles operations such as flashing, resetting, halting, stepping, setting breakpoints, and reading memory. OpenOCD, probe-rs, and pyocd can serve this role. section 6.1.2 section 6.5.5
source [find interface/stlink.cfg] source [find target/stm32f1x.cfg]
A minimal OpenOCD configuration names the attached debug adapter and target chip. section 6.5.5
A typical session starts the server separately, connects GDB to its TCP port, then loads firmware and resets the target. OpenOCD commonly listens on port 3333; GDB can connect with extended-remote mode. section 6.5.4 section 6.5.6
