aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2006-03-09 21:44:27 +0000
committerJim Blandy <jimb@codesourcery.com>2006-03-09 21:44:27 +0000
commit66b8c7f6577693f81636d0f256cdd01a9ddbaf04 (patch)
tree8fe7f54711df572094318b77c021b95f8cb493b2 /gdb
parent1a10341b71c374c8dec3007661c0843b803debe8 (diff)
downloadgdb-66b8c7f6577693f81636d0f256cdd01a9ddbaf04.zip
gdb-66b8c7f6577693f81636d0f256cdd01a9ddbaf04.tar.gz
gdb-66b8c7f6577693f81636d0f256cdd01a9ddbaf04.tar.bz2
2006-03-07 Jim Blandy <jimb@red-bean.com>
* gdb.texinfo (Connecting): Document 'target remote pipe'.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/doc/ChangeLog2
-rw-r--r--gdb/doc/gdb.texinfo14
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