Gdbserver
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Gdbserver" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Gdbserver|concern=non-notable and written like a how to.}} ~~~~Timestamp: 20100211235555 23:55, 11 February 2010 (UTC) Administrators: delete |
 |
gdbserver is a program that allows to remotely debug with the GNU Debugger. It runs as a command-line tool on many Unix-like systems.[clarification needed]
It only needs the presence of the executable on the target, while the source code stays in the computer used by the developper (with also a copy of the binary file).
How It Works
- gdbserver is launched on the target with the path and name of the executable to debug, and a port number (TCP or UDP). It listens for connections on the port.
- gdb is run on the host with the path and name of the executable (and the sources) on the host, and the IP address and port number to connect to the target.
This is a example of a command to run on the target (where "hello_world" is the name of the executable and "2345" the TCP port number):
gdbserver hello_world :2345
From the host side, {{{gdb}}} is run in the standard way
gdb hello_world
and then needs to connect
target remote 192.168.0.11:2345