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

* gdb.texinfo (Dump/Restore Files): Update documentation for

Browse Source 
'dump', 'append', and 'restore': note that format argument is
optional; simplify presentation of the command variants; and be
more precise about the formats.
This commit is contained in:
Jim Blandy
2003-05-08 21:33:49 +00:00
parent d9d9c31f31
commit df5215a60c
2 changed files with 46 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
gdb/doc/ChangeLog
View File

@ -1,3 +1,10 @@
2003-05-08 Jim Blandy <jimb@redhat.com>
* gdb.texinfo (Dump/Restore Files): Update documentation for
'dump', 'append', and 'restore': note that format argument is
optional; simplify presentation of the command variants; and be
more precise about the formats.
2003-05-07 Jim Blandy <jimb@redhat.com> 2003-05-07 Jim Blandy <jimb@redhat.com>
* gdb.texinfo (Symbols): Update documentation: 'maint list * gdb.texinfo (Symbols): Update documentation: 'maint list

87
gdb/doc/gdb.texinfo
View File

@ -5861,62 +5861,53 @@ Disable @value{GDBN} from caching target memory. This is the default.
@cindex append data to a file @cindex append data to a file
@cindex dump data to a file @cindex dump data to a file
@cindex restore data from a file @cindex restore data from a file
@kindex dump
@kindex append
@kindex restore
The commands @code{dump}, @code{append}, and @code{restore} are used You can use the commands @code{dump}, @code{append}, and
for copying data between target memory and a file. Data is written @code{restore} to copy data between target memory and a file. The
into a file using @code{dump} or @code{append}, and restored from a @code{dump} and @code{append} commands write data to a file, and the
file into memory by using @code{restore}. Files may be binary, srec, @code{restore} command reads data from a file back into the inferior's
intel hex, or tekhex (but only binary files can be appended). memory. Files may be in binary, Motorola S-record, Intel hex, or
Tektronix Hex format; however, @value{GDBN} can only append to binary
files.
@table @code @table @code
@kindex dump binary
@kindex append binary
@item dump binary memory @var{filename} @var{start_addr} @var{end_addr}
Dump contents of memory from @var{start_addr} to @var{end_addr} into
raw binary format file @var{filename}.
@item append binary memory @var{filename} @var{start_addr} @var{end_addr} @kindex dump
Append contents of memory from @var{start_addr} to @var{end_addr} to @item dump @r{[}@var{format}@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
raw binary format file @var{filename}. @itemx dump @r{[}@var{format}@r{]} value @var{filename} @var{expr}
Dump the contents of memory from @var{start_addr} to @var{end_addr},
or the value of @var{expr}, to @var{filename} in the given format.
@item dump binary value @var{filename} @var{expression} The @var{format} parameter may be any one of:
Dump value of @var{expression} into raw binary format file @var{filename}. @table @code
@item binary
Raw binary form.
@item ihex
Intel hex format.
@item srec
Motorola S-record format.
@item tekhex
Tektronix Hex format.
@end table
@item append binary memory @var{filename} @var{expression} @value{GDBN} uses the same definitions of these formats as the
Append value of @var{expression} to raw binary format file @var{filename}. @sc{gnu} binary utilities, like @samp{objdump} and @samp{objcopy}. If
@var{format} is omitted, @value{GDBN} dumps the data in raw binary
form.
@kindex dump ihex @kindex append
@item dump ihex memory @var{filename} @var{start_addr} @var{end_addr} @item append @r{[}binary@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
Dump contents of memory from @var{start_addr} to @var{end_addr} into @itemx append @r{[}binary@r{]} value @var{filename} @var{expr}
intel hex format file @var{filename}. Append the contents of memory from @var{start_addr} to @var{end_addr},
or the value of @var{expr}, to @var{filename}, in raw binary form.
(@value{GDBN} can only append data to files in raw binary form.)
@item dump ihex value @var{filename} @var{expression} @kindex restore
Dump value of @var{expression} into intel hex format file @var{filename}. @item restore @var{filename} @r{[}binary@r{]} @var{bias} @var{start} @var{end}
Restore the contents of file @var{filename} into memory. The
@kindex dump srec @code{restore} command can automatically recognize any known @sc{bfd}
@item dump srec memory @var{filename} @var{start_addr} @var{end_addr} file format, except for raw binary. To restore a raw binary file you
Dump contents of memory from @var{start_addr} to @var{end_addr} into must specify the optional keyword @code{binary} after the filename.
srec format file @var{filename}.
@item dump srec value @var{filename} @var{expression}
Dump value of @var{expression} into srec format file @var{filename}.
@kindex dump tekhex
@item dump tekhex memory @var{filename} @var{start_addr} @var{end_addr}
Dump contents of memory from @var{start_addr} to @var{end_addr} into
tekhex format file @var{filename}.
@item dump tekhex value @var{filename} @var{expression}
Dump value of @var{expression} into tekhex format file @var{filename}.
@item restore @var{filename} [@var{binary}] @var{bias} @var{start} @var{end}
Restore the contents of file @var{filename} into memory. The @code{restore}
command can automatically recognize any known bfd file format, except for
raw binary. To restore a raw binary file you must use the optional argument
@var{binary} after the filename.
If @var{bias} is non-zero, its value will be added to the addresses If @var{bias} is non-zero, its value will be added to the addresses
contained in the file. Binary files always start at address zero, so contained in the file. Binary files always start at address zero, so