Gdbserver: Difference between revisions

Revision as of 05:41, 16 January 2016

Latest revision as of 23:35, 29 July 2024

(9 intermediate revisions by 8 users not shown)

Line 1:

{{Short description|Remote debugging program}}

{{lowercase|title=gdbserver}}

'''gdbserver''' is a computer program that makes it possible to remotely [[Debugging|debug]] other programs.<ref>[http://ftp.gnu.org/old-gnu/Manuals/gdb-5.1.1/html_node/gdb_130.html GDB Manual]</ref> Running on the same system as the program to be debugged, it allows the [[GNU Debugger]] to connect from another system; that is, only the executable to be debugged needs to be resident on the target system ("target"), while the source code and a copy of the binary file to be debugged reside on the developer’sdeveloper's local computer ("host"). The connection can be either TCP or a serial line.

== How it works ==

# <code>gdbserver</code> is launched on the target system, with the arguments:

#* Either a device name (to use a serial line) or a TCP hostname and portnumberport number, and

#* The path and filename of the executable to be debugged

#:It then waits passively for the host gdb to communicate with it.

Line 11 ⟶ 12:

#* A device name (for a serial line) or the IP address and port number needed for connection to the target system.

Example for debugging a program called <code>hello_world</code> on a remote target using TCP ("2159" is the [[List_of_TCP_and_UDP_port_numbersList of TCP and UDP port numbers#Registered_portsRegistered ports|registered TCP port number for remote GDB]]):

<sourcesyntaxhighlight lang="console">

remote@~$ gdbserver :2159 hello_world

Process hello_world created; pid = 2509

Listening on port 2159

</syntaxhighlight>

</source>

<sourcesyntaxhighlight lang="console">

local@~$ gdb -q hello_world

Reading symbols from /home/user/hello_world...done.

Line 31 ⟶ 32:

10 printf("x[%d] = %g\n", i, x[i]);

(gdb)

</syntaxhighlight>

</source>

== Alternatives ==

Another technique for debugging programs remotely is to use a ''remote stub''.<ref>[httphttps://davissourceware.lbl.govorg/gdb/Manualsonlinedocs/GDBgdb/gdb_17Remote-Stub.html#SEC140 Debugging with GDB]</ref>{{Clarify|date=February 2010}} In this case, the program to be debugged is linked with a few special-purpose subroutines that implement the GDB remote serial protocol. The file containing these subroutines is called a "debugging stub".

== See also ==

Line 44 ⟶ 45:

== References ==

* Andreas Zeller: <cite>Why Programs Fail: A Guide to Systematic Debugging</cite>, Morgan Kaufmann, 2005. {{ISBN |1-55860-866-4}}

== External links ==