OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

* gdb.texinfo (Target Commands): Update text describing how to
	specify a target.  Refer to the detailed section on remote
	debugging, not the brief mention.
This commit is contained in:
Jim Blandy 2006-03-09 21:42:31 +00:00
parent 14288fdc16
commit 1a10341b71
2 changed files with 20 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/doc/ChangeLog
View File

@ -1,5 +1,9 @@
2006-03-07 Jim Blandy <jimb@red-bean.com> 2006-03-07 Jim Blandy <jimb@red-bean.com>
* gdb.texinfo (Target Commands): Update text describing how to
specify a target. Refer to the detailed section on remote
debugging, not the brief mention.
* gdb.texinfo (Connecting): Organize the different 'target remote' * gdb.texinfo (Connecting): Organize the different 'target remote'
connection methods into a table. Add a 'target remote' index connection methods into a table. Add a 'target remote' index
entry. (!!!) entry. (!!!)

23
gdb/doc/gdb.texinfo
View File

@ -11906,14 +11906,23 @@ An executable file. @samp{target exec @var{program}} is the same as
A core dump file. @samp{target core @var{filename}} is the same as A core dump file. @samp{target core @var{filename}} is the same as
@samp{core-file @var{filename}}. @samp{core-file @var{filename}}.
@item target remote @var{dev} @item target remote @var{medium}
@cindex remote target @cindex remote target
Remote serial target in GDB-specific protocol. The argument @var{dev} A remote system connected to @value{GDBN} via a serial line or network
specifies what serial device to use for the connection (e.g.@: connection. This command tells @value{GDBN} to use its own remote
@file{/dev/ttya}). @xref{Remote, ,Remote debugging}. @code{target remote} protocol over @var{medium} for debugging. @xref{Remote Debugging}.
supports the @code{load} command. This is only useful if you have
some other way of getting the stub to the target system, and you can put For example, if you have a board connected to @file{/dev/ttya} on the
it somewhere in memory where it won't get clobbered by the download. machine running @value{GDBN}, you could say:
@smallexample
target remote /dev/ttya
@end smallexample
@code{target remote} supports the @code{load} command. This is only
useful if you have some other way of getting the stub to the target
system, and you can put it somewhere in memory where it won't get
clobbered by the download.
@item target sim @item target sim
@cindex built-in simulator target @cindex built-in simulator target