Content deleted Content added
m Replace magic links with templates per local RfC and MediaWiki RfC |
Sammi Brie (talk | contribs) Adding short description: "Remote debugging program" |
||
(8 intermediate revisions by 7 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
== 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
#* 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 [[
<
remote@~$ gdbserver :2159 hello_world
Process hello_world created; pid = 2509
Listening on port 2159
</syntaxhighlight>
<
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>
== Alternatives ==
Another technique for debugging programs remotely is to use a ''remote stub''.<ref>[
== See also ==
|