diff options
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/ChangeLog | 2 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 14 |
2 files changed, 16 insertions, 0 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 7d0c9bb..6345276 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,5 +1,7 @@ 2006-03-07 Jim Blandy <jimb@red-bean.com> + * gdb.texinfo (Connecting): Document 'target remote pipe'. + * gdb.texinfo (Target Commands): Update text describing how to specify a target. Refer to the detailed section on remote debugging, not the brief mention. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 6fc2a3a..15dd18d 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -12219,6 +12219,20 @@ keep in mind that the `U' stands for ``Unreliable''. @acronym{UDP} can silently drop packets on busy or unreliable networks, which will cause havoc with your debugging session. +@item target remote | @var{command} +@cindex pipe, @code{target remote} to +Run @var{command} in the background and communicate with it using a +pipe. The @var{command} is a shell command, to be parsed and expanded +by the system's command shell, @code{/bin/sh}; it should expect remote +protocol packets on its standard input, and send replies on its +standard output. You could use this to run a stand-alone simulator +that speaks the remote debugging protocol, to make net connections +using programs like @code{ssh}, or for other similar tricks. + +If @var{command} closes its standard output (perhaps by exiting), +@value{GDBN} will try to send it a @code{SIGTERM} signal. (If the +program has already exited, this will have no effect.) + @end table Once the connection has been established, you can use all the usual |