espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-20 01:50:24 +08:00
Code Issues Packages Projects Releases Wiki Activity

2006-03-07 Jim Blandy <jimb@red-bean.com>

Browse Source 
* gdb.texinfo (Connecting): Document 'target remote pipe'.
This commit is contained in:
Jim Blandy
2006-03-09 21:44:27 +00:00
parent 1a10341b71
commit 66b8c7f657
2 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
gdb/doc/ChangeLog
View File

@ -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.

14
gdb/doc/gdb.texinfo
View File

@ -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