gdbinv-s.texi, gdb.texinfo: include Hitachi SH target
gdb.texinfo: advance manual revision dates to present gdbinv-s.texi, gdb.texinfo, all-config.texi, h8-config.texi: stop using silly Roman numerals in @set variable names
This commit is contained in:
parent
9a5e3a9ac5
commit
a64a6c2b7d
5 changed files with 109 additions and 72 deletions
|
@ -1,3 +1,12 @@
|
|||
Fri Apr 23 17:21:13 1993 Roland H. Pesch (pesch@fowanton.cygnus.com)
|
||||
|
||||
* gdbinv-s.texi, gdb.texinfo: include Hitachi SH target
|
||||
|
||||
* gdb.texinfo: advance manual revision dates to present
|
||||
|
||||
* gdbinv-s.texi, gdb.texinfo, all-config.texi, h8-config.texi:
|
||||
stop using silly Roman numerals in @set variable names
|
||||
|
||||
Fri Apr 23 07:30:01 1993 Jim Kingdon (kingdon@cygnus.com)
|
||||
|
||||
* stabs.texinfo (Parameters): Keep trying to get this right.
|
||||
|
|
|
@ -19,24 +19,24 @@
|
|||
@set GENERIC
|
||||
@c
|
||||
@c Hitachi H8/300 target:
|
||||
@set Hviii
|
||||
@set H8
|
||||
@c Hitachi H8/300 target ONLY:
|
||||
@clear HviiiEXCLUSIVE
|
||||
@clear H8EXCLUSIVE
|
||||
@c
|
||||
@c SPARC target:
|
||||
@set SPARC
|
||||
@c
|
||||
@c AMD 29000 target:
|
||||
@set AMDxxixK
|
||||
@set AMD29K
|
||||
@c
|
||||
@c Intel 960 target:
|
||||
@set Icmlx
|
||||
@set I960
|
||||
@c
|
||||
@c Tandem ST2000 (phone switch) target:
|
||||
@set STmm
|
||||
@set ST2000
|
||||
@c
|
||||
@c Zilog 8000 target:
|
||||
@set ZviiiK
|
||||
@set Z8K
|
||||
@c
|
||||
@c Lucid "Energize" environment:
|
||||
@clear LUCID
|
||||
|
|
|
@ -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
|
||||
|
|
|
@ -339,7 +339,7 @@ stream. @code{set remotedebug off} turns it off, and @code{show
|
|||
remotedebug} will show you its current state.
|
||||
@end ifset
|
||||
|
||||
@ifset Icmlx
|
||||
@ifset I960
|
||||
@node i960-Nindy Remote
|
||||
@subsection @value{GDBN} with a remote i960 (Nindy)
|
||||
|
||||
|
@ -444,7 +444,7 @@ a break is detected.
|
|||
@c @end group
|
||||
@end ifset
|
||||
|
||||
@ifset AMDxxixK
|
||||
@ifset AMD29K
|
||||
@node UDI29K Remote
|
||||
@subsection @value{GDBN} and the UDI protocol for AMD29K
|
||||
|
||||
|
@ -655,7 +655,7 @@ unexpected events on the PC side of the connection.
|
|||
|
||||
@end ifset
|
||||
|
||||
@ifset STmm
|
||||
@ifset ST2000
|
||||
@node ST2000 Remote
|
||||
@subsection @value{GDBN} with a Tandem ST2000
|
||||
|
||||
|
@ -836,16 +836,17 @@ or suspended when you attach to it. If running, it will be suspended at
|
|||
the time of attachment.
|
||||
@end ifset
|
||||
|
||||
@ifset Hviii
|
||||
@node Hitachi H8 Remote
|
||||
@subsection @value{GDBN} and the Hitachi H8/300 and H8/500
|
||||
@value{GDBN} needs to know these things to talk to your H8/300 or H8/500:
|
||||
@ifset H8
|
||||
@node Hitachi Remote
|
||||
@subsection @value{GDBN} and Hitachi Microprocessors
|
||||
@value{GDBN} needs to know these things to talk to your
|
||||
Hitachi SH, H8/300, or H8/500:
|
||||
|
||||
@enumerate
|
||||
@item
|
||||
that you want to use @samp{target hms}, the remote debugging
|
||||
interface for the H8/300 and H8/500 (this is the default when
|
||||
GDB is configured specifically for the H8/300 or H8/500);
|
||||
that you want to use @samp{target hms}, the remote debugging interface
|
||||
for Hitachi microprocessors (this is the default when GDB is configured
|
||||
specifically for the Hitachi SH, H8/300, or H8/500);
|
||||
|
||||
@item
|
||||
what serial device connects your host to your Hitachi board (the first
|
||||
|
@ -858,32 +859,37 @@ what speed to use over the serial device.
|
|||
@end ignore
|
||||
@end enumerate
|
||||
|
||||
@ignore
|
||||
@ifclear H8EXCLUSIVE
|
||||
@c only for Unix hosts
|
||||
@kindex device
|
||||
@cindex serial device, H8/300 or H8/500
|
||||
@cindex serial device, Hitachi micros
|
||||
Use the special @code{@value{GDBP}} command @samp{device @var{port}} if you
|
||||
need to explicitly set the serial device. The default @var{port} is the
|
||||
first available port on your host. This is only necessary on Unix
|
||||
hosts, where it is typically something like @file{/dev/ttya}.
|
||||
|
||||
@kindex speed
|
||||
@cindex serial line speed, H8/300 or H8/500
|
||||
@cindex serial line speed, Hitachi micros
|
||||
@code{@value{GDBP}} has another special command to set the communications
|
||||
speed: @samp{speed @var{bps}}. This command also is only used from Unix
|
||||
hosts; on DOS hosts, set the line speed as usual from outside GDB with
|
||||
the DOS @kbd{mode} command (for instance, @w{@samp{mode
|
||||
com2:9600,n,8,1,p}} for a 9600 bps connection).
|
||||
@end ignore
|
||||
|
||||
The @samp{device} and @samp{speed} commands are available only when you
|
||||
use a Unix host to debug your Hitachi microprocessor programs. If you
|
||||
use a DOS host,
|
||||
@end ifclear
|
||||
@value{GDBN} depends on an auxiliary terminate-and-stay-resident program
|
||||
called @code{asynctsr} to communicate with the development board
|
||||
through a PC serial port. You must also use the DOS @code{mode} command
|
||||
to set up the serial port on the DOS side.
|
||||
|
||||
@ifset DOSHOST
|
||||
The following sample session illustrates the steps needed to start a
|
||||
program under @value{GDBN} control on an H8/300. The example uses a sample
|
||||
H8/300 program called @file{t.x}.
|
||||
program under @value{GDBN} control on an H8/300. The example uses a
|
||||
sample H8/300 program called @file{t.x}. The procedure is the same for
|
||||
the Hitachi SH and the H8/500.
|
||||
|
||||
First hook up your development board. In this example, we use a
|
||||
board attached to serial port @code{COM2}; if you use a different serial
|
||||
|
@ -966,6 +972,7 @@ to detect program completion.
|
|||
In either case, @value{GDBN} will see the effect of a @sc{reset} on the
|
||||
development board as a ``normal exit'' of your program.
|
||||
@end ifset
|
||||
@end ifset
|
||||
|
||||
@ifset SIMS
|
||||
@node Simulator
|
||||
|
@ -974,25 +981,30 @@ development board as a ``normal exit'' of your program.
|
|||
@ifset GENERIC
|
||||
@cindex simulator
|
||||
@cindex simulator, Z8000
|
||||
@cindex simulator, H8/300 or H8/500
|
||||
@cindex Z8000 simulator
|
||||
@cindex simulator, H8/300 or H8/500
|
||||
@cindex H8/300 or H8/500 simulator
|
||||
@cindex simulator, Hitachi SH
|
||||
@cindex Hitachi SH simulator
|
||||
@cindex CPU simulator
|
||||
For some configurations, @value{GDBN} includes a CPU simulator that you
|
||||
can use instead of a hardware CPU to debug your programs. Currently,
|
||||
a simulator is available when @value{GDBN} is configured to debug Zilog
|
||||
Z8000 or Hitachi H8/300 or H8/500 targets.
|
||||
Z8000 or Hitachi microprocessor targets.
|
||||
@end ifset
|
||||
|
||||
@ifclear GENERIC
|
||||
@ifset Hviii
|
||||
@ifset H8
|
||||
@cindex simulator, H8/300 or H8/500
|
||||
@cindex Hitachi H8/300 or H8/500 simulator
|
||||
When configured for debugging Hitachi H8/300 or H8/500 targets,
|
||||
@value{GDBN} includes an H8/300 or H8/500 CPU simulator.
|
||||
@cindex simulator, Hitachi SH
|
||||
@cindex Hitachi SH simulator
|
||||
When configured for debugging Hitachi microprocessor targets,
|
||||
@value{GDBN} includes a CPU simulator for the target chip (a Hitachi SH,
|
||||
H8/300, or H8/500).
|
||||
@end ifset
|
||||
|
||||
@ifset ZviiiK
|
||||
@ifset Z8K
|
||||
@cindex simulator, Z8000
|
||||
@cindex Zilog Z8000 simulator
|
||||
When configured for debugging Zilog Z8000 targets, @value{GDBN} includes
|
||||
|
@ -1000,7 +1012,7 @@ a Z8000 simulator.
|
|||
@end ifset
|
||||
@end ifclear
|
||||
|
||||
@ifset ZviiiK
|
||||
@ifset Z8K
|
||||
For the Z8000 family, @samp{target sim} simulates either the Z8002 (the
|
||||
unsegmented variant of the Z8000 architecture) or the Z8001 (the
|
||||
segmented variant). The simulator recognizes which architecture is
|
||||
|
|
|
@ -2,15 +2,16 @@
|
|||
@include GDBvn.texi
|
||||
@c
|
||||
@set AGGLOMERATION
|
||||
@clear AMDxxixK
|
||||
@clear AMD29K
|
||||
@set BARETARGET
|
||||
@set CONLY
|
||||
@set DOSHOST
|
||||
@clear FSFDOC
|
||||
@clear GENERIC
|
||||
@set Hviii
|
||||
@set HviiiEXCLUSIVE
|
||||
@clear Icmlx
|
||||
@set H8
|
||||
@set H8EXCLUSIVE
|
||||
@clear HAVE-FLOAT
|
||||
@clear I960
|
||||
@clear NOVEL
|
||||
@clear POSIX
|
||||
@set PRECONFIGURED
|
||||
|
@ -18,9 +19,9 @@
|
|||
@set SIMS
|
||||
@clear SERIAL
|
||||
@clear SPARC
|
||||
@clear STmm
|
||||
@clear ST2000
|
||||
@clear VXWORKS
|
||||
@clear ZviiiK
|
||||
@clear Z8K
|
||||
@c ----------------------------------------------------------------------
|
||||
@c STRINGS:
|
||||
@c
|
||||
|
@ -34,7 +35,7 @@
|
|||
@set GDBINIT .gdbinit
|
||||
@c
|
||||
@c Name of target.
|
||||
@set TARGET Hitachi H/300 and H/500
|
||||
@set TARGET Hitachi Microprocessors
|
||||
@c
|
||||
@c Name of GCC product
|
||||
@set NGCC GCC
|
||||
|
|
Loading…
Reference in a new issue