diff options
Diffstat (limited to 'gdb/doc/gdb.texinfo')
| -rw-r--r-- | gdb/doc/gdb.texinfo | 87 |
1 files changed, 51 insertions, 36 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index e1b33b6..eb72f4d 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -73,7 +73,7 @@ END-INFO-DIR-ENTRY This file documents the GNU debugger @value{GDBN}. @c !!set edition, date, version -This is Edition 4.07, January 1993, +This is Edition 4.09, April 1993, of @cite{Debugging with @value{GDBN}: the GNU Source-Level Debugger} for GDB Version @value{GDBVN}. @@ -108,12 +108,12 @@ instead of in the original English. @title Debugging with @value{GDBN} @subtitle The GNU Source-Level Debugger @ifclear GENERIC -@subtitle on @value{TARGET} Systems +@subtitle (@value{TARGET}) @end ifclear @sp 1 @c !!set edition, date, version -@subtitle Edition 4.07, for @value{GDBN} version @value{GDBVN} -@subtitle January 1993 +@subtitle Edition 4.09, for @value{GDBN} version @value{GDBVN} +@subtitle April 1993 @author by Richard M. Stallman and Roland H. Pesch @page @tex @@ -154,7 +154,7 @@ instead of in the original English. This file describes @value{GDBN}, the GNU symbolic debugger. @c !!set edition, date, version -This is Edition 4.07, January 1993, for GDB Version @value{GDBVN}. +This is Edition 4.09, April 1993, for GDB Version @value{GDBVN}. @menu * Summary:: Summary of @value{GDBN} @@ -341,7 +341,7 @@ He also enhanced the command-completion support to cover C++ overloaded symbols. @end ifclear -Hitachi America, Ltd. sponsored the support for the H8/300 and H8/500. +Hitachi America, Ltd. sponsored the support for Hitachi microprocessors. @ifset NOVEL @node New Features @@ -718,10 +718,10 @@ or @kbd{C-d} to exit.) @node Invoking GDB @section Invoking @value{GDBN} -@ifset HviiiEXCLUSIVE +@ifset H8EXCLUSIVE For details on starting up @value{GDBP} as a -remote debugger attached to a Hitachi H8/300 or H8/500 board, see @ref{Hitachi -H8 Remote,,@value{GDBN} and the Hitachi H8/300 and H8/500}. +remote debugger attached to a Hitachi microprocessor, see @ref{Hitachi +Remote,,@value{GDBN} and Hitachi Microprocessors}. @end ifset Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started, @@ -794,21 +794,21 @@ in sequential order. The order makes a difference when the @ifset REMOTESTUB * Remote Serial:: @value{GDBN} remote serial protocol @end ifset -@ifset Icmlx +@ifset I960 * i960-Nindy Remote:: @value{GDBN} with a remote i960 (Nindy) @end ifset -@ifset AMDxxixK +@ifset AMD29K * UDI29K Remote:: @value{GDBN} and the UDI protocol for AMD29K * EB29K Remote:: @value{GDBN} with a remote EB29K @end ifset @ifset VXWORKS * VxWorks Remote:: @value{GDBN} and VxWorks @end ifset -@ifset STmm +@ifset ST2000 * ST2000 Remote:: @value{GDBN} with a Tandem ST2000 @end ifset -@ifset Hviii -* Hitachi H8 Remote:: @value{GDBN} and the Hitachi H8/300 and H8/500 +@ifset H8 +* Hitachi Remote:: @value{GDBN} and Hitachi Microprocessors @end ifset @ifset SIMS * Simulator:: Simulated CPU target @@ -3476,7 +3476,7 @@ will be dumped. Two arguments specify a range of addresses (first inclusive, second exclusive) to dump. @end table -@ifclear HviiiEXCLUSIVE +@ifclear H8EXCLUSIVE We can use @code{disassemble} to inspect the object code range shown in the last @code{info line} example (the example shows SPARC machine instructions): @@ -3497,7 +3497,7 @@ End of assembler dump. @end smallexample @end ifclear -@ifset HviiiEXCLUSIVE +@ifset H8EXCLUSIVE For example, here is the beginning of the output for the disassembly of a function @code{fact}: @@ -3575,7 +3575,7 @@ command rather than @code{print}. @xref{Symbols, ,Examining the Symbol Table}. * Value History:: Value history * Convenience Vars:: Convenience variables * Registers:: Registers -@ifclear HviiiEXCLUSIVE +@ifclear HAVE-FLOAT * Floating Point Hardware:: Floating point hardware @end ifclear @end menu @@ -4558,7 +4558,7 @@ code generated by your compiler. If some registers are not saved, or if @value{GDBN} is unable to locate the saved registers, the selected stack frame will make no difference. -@ifset AMDxxixK +@ifset AMD29K @table @code @item set rstack_high_address @var{address} @kindex set rstack_high_address @@ -4581,7 +4581,7 @@ processors. @end table @end ifset -@ifclear HviiiEXCLUSIVE +@ifclear HAVE-FLOAT @node Floating Point Hardware @section Floating point hardware @cindex floating point @@ -6487,18 +6487,26 @@ On VxWorks, @code{load} will dynamically link @var{filename} on the current target system as well as adding its symbols in @value{GDBN}. @end ifset -@ifset Icmlx +@ifset I960 @cindex download to Nindy-960 With the Nindy interface to an Intel 960 board, @code{load} will download @var{filename} to the 960 as well as adding its symbols in @value{GDBN}. @end ifset -@ifset Hviii +@ifset H8 @cindex download to H8/300 or H8/500 @cindex H8/300 or H8/500 download -When you select remote debugging to a Hitachi H8/300 or H8/500 board -(@pxref{Hitachi H8 Remote,,@value{GDBN} and the Hitachi H8/300 and H8/500}), +@c start-sanitize-Hitachi-SH +@cindex download to Hitachi SH +@cindex Hitachi SH download +@c end-sanitize-Hitachi-SH +When you select remote debugging to a Hitachi +@c start-sanitize-Hitachi-SH +SH, +@c end-sanitize-Hitachi-SH +H8/300, or H8/500 board +(@pxref{Hitachi Remote,,@value{GDBN} and Hitachi Microprocessors}), the @code{load} command downloads your program to the Hitachi board and also opens it as the current executable target for @value{GDBN} on your host (like the @code{file} command). @@ -6815,7 +6823,7 @@ specifies what serial device to use for the connection (e.g. CPU simulator. @xref{Simulator,,Simulated CPU Target}. @end ifset -@ifset AMDxxixK +@ifset AMD29K @item target udi @var{keyword} @kindex target udi Remote AMD29K target, using the AMD UDI protocol. The @var{keyword} @@ -6832,16 +6840,23 @@ name of the program to be debugged, as it appears to DOS on the PC. @xref{EB29K Remote, ,@value{GDBN} with a remote EB29K}. @end ifset -@ifset Hviii +@ifset H8 @item target hms @kindex target hms -A Hitachi H8/300 or H8/500 board, attached via serial line to your host. Use -special commands @code{device} and @code{speed} to control the serial -line and the communications speed used. @xref{Hitachi H8 -Remote,,@value{GDBN} and the Hitachi H8/300 and H8/500}. +A Hitachi +@c start-sanitize-Hitachi-SH +SH, +@c end-sanitize-Hitachi-SH +H8/300, or H8/500 board, attached via serial line to your host. +@ifclear H8EXCLUSIVE +@c Unix only, not currently of interest for H8-only manual +Use special commands @code{device} and @code{speed} to control the serial +line and the communications speed used. +@end ifclear +@xref{Hitachi Remote,,@value{GDBN} and Hitachi Microprocessors}. @end ifset -@ifset Icmlx +@ifset I960 @item target nindy @var{devicename} @kindex target nindy An Intel 960 board controlled by a Nindy Monitor. @var{devicename} is @@ -6849,7 +6864,7 @@ the name of the serial device to use for the connection, e.g. @file{/dev/ttya}. @xref{i960-Nindy Remote, ,@value{GDBN} with a remote i960 (Nindy)}. @end ifset -@ifset STmm +@ifset ST2000 @item target st2000 @var{dev} @var{speed} @kindex target st2000 A Tandem ST2000 phone switch, running Tandem's STDBUG protocol. @var{dev} @@ -6901,21 +6916,21 @@ configuration of GDB; use @code{help targets} to list them. @ifset REMOTESTUB * Remote Serial:: @value{GDBN} remote serial protocol @end ifset -@ifset Icmlx +@ifset I960 * i960-Nindy Remote:: @value{GDBN} with a remote i960 (Nindy) @end ifset -@ifset AMDxxixK +@ifset AMD29K * UDI29K Remote:: @value{GDBN} and the UDI protocol for AMD29K * EB29K Remote:: @value{GDBN} with a remote EB29K @end ifset @ifset VXWORKS * VxWorks Remote:: @value{GDBN} and VxWorks @end ifset -@ifset STmm +@ifset ST2000 * ST2000 Remote:: @value{GDBN} with a Tandem ST2000 @end ifset -@ifset Hviii -* Hitachi H8 Remote:: @value{GDBN} and the Hitachi H8/300 and H8/500 +@ifset H8 +* Hitachi Remote:: @value{GDBN} and Hitachi Microprocessors @end ifset @ifset SIMS * Simulator:: Simulated CPU target |