Chapter 20. Configuration-Specific Information
179
20.3.13. Tandem ST2000
gdb may be used with a Tandem ST2000 phone switch, running Tandem’s STDBUG protocol.
To connect your ST2000 to the host system, see the manufacturer’s manual. Once the ST2000 is
physically attached, you can run:
target st2000
dev speed
to establish it as your debugging environment.
dev
is normally the name of a serial device, such as
/dev/ttya
, connected to the ST2000 via a serial line. You can instead specify
dev
as a TCP
connection (for example, to a serial line attached via a terminal concentrator) using the syntax
hostname
:
portnumber
.
The
load
and
attach
commands are
not
defined for this target; you must load your program into the
ST2000 as you normally would for standalone operation. gdb reads debugging information (such as
symbols) from a separate, debugging version of the program available on your host computer.
These auxiliary gdb commands are available to help you with the ST2000 environment:
st2000
command
Send a
command
to the STDBUG monitor. See the manufacturer’s manual for available com-
mands.
connect
Connect the controlling terminal to the STDBUG command monitor. When you are done inter-
acting with STDBUG, typing either of two character sequences gets you back to the gdb com-
mand prompt:
[RET]~.
(Return, followed by tilde and period) or
[RET]~[C-d]
(Return,
followed by tilde and control-D).
20.3.14. Zilog Z8000
When configured for debugging Zilog Z8000 targets, gdb includes a Z8000 simulator.
For the Z8000 family,
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
appropriate by inspecting the object code.
target sim
args
Debug programs on a simulated CPU. If the simulator supports setup options, specify them via
args
.
After specifying this target, you can debug programs for the simulated CPU in the same style as
programs for your host computer; use the
file
command to load a new program image, the
run
command to run your program, and so on.
As well as making available all the usual machine registers (refer to Section 10.10
Registers
), the
Z8000 simulator provides three additional items of information as specially named registers:
cycles
Counts clock-ticks in the simulator.
insts
Counts instructions run in the simulator.
Summary of Contents for ENTERPRISE LINUX 4 - DEVELOPER TOOLS GUIDE
Page 1: ...Red Hat Enterprise Linux 4 Debugging with gdb ...
Page 12: ...2 Chapter 1 Debugging with gdb ...
Page 28: ...18 Chapter 4 Getting In and Out of gdb ...
Page 34: ...24 Chapter 5 gdb Commands ...
Page 44: ...34 Chapter 6 Running Programs Under gdb ...
Page 68: ...58 Chapter 8 Examining the Stack ...
Page 98: ...88 Chapter 10 Examining Data ...
Page 112: ...102 Chapter 12 Tracepoints ...
Page 118: ...108 Chapter 13 Debugging Programs That Use Overlays ...
Page 138: ...128 Chapter 14 Using gdb with Different Languages ...
Page 144: ...134 Chapter 15 Examining the Symbol Table ...
Page 170: ...160 Chapter 19 Debugging remote programs ...
Page 198: ...188 Chapter 21 Controlling gdb ...
Page 204: ...194 Chapter 22 Canned Sequences of Commands ...
Page 206: ...196 Chapter 23 Command Interpreters ...
Page 216: ...206 Chapter 25 Using gdb under gnu Emacs ...
Page 296: ...286 Chapter 27 gdb Annotations ...
Page 300: ...290 Chapter 28 Reporting Bugs in gdb ...
Page 322: ...312 Chapter 30 Using History Interactively ...
Page 362: ...352 Appendix D gdb Remote Serial Protocol ...
Page 380: ...370 Appendix F GNU GENERAL PUBLIC LICENSE ...
Page 386: ...376 Appendix G GNU Free Documentation License ...
Page 410: ......