from gdb.texinfo on 11 July 1994 -->
Debugging with GDB - Target Commands
Go to the previous, next section.
target type parameters
- Connects the GDB host environment to a target
machine or process. A target is typically a protocol for talking to
debugging facilities. You use the argument type to specify the
type or protocol of the target machine.
Further parameters are interpreted by the target protocol, but
typically include things like device names or host names to connect
with, process numbers, and baud rates.
The target
command does not repeat if you press RET again
after executing the command.
help target
-
Displays the names of all targets available. To display targets
currently selected, use either
info target
or info files
(see section Commands to specify files).
help target name
- Describe a particular target, including any parameters necessary to
select it.
Here are some common targets (available, or not, depending on the GDB
configuration):
target exec program
-
An executable file. `target exec program' is the same as
`exec-file program'.
target core filename
-
A core dump file. `target core filename' is the same as
`core-file filename'.
target remote dev
-
Remote serial target in GDB-specific protocol. The argument dev
specifies what serial device to use for the connection (e.g.
`/dev/ttya'). See section Remote debugging.
target sim
-
CPU simulator. See section Simulated CPU target.
target udi keyword
-
Remote AMD29K target, using the AMD UDI protocol. The keyword
argument specifies which 29K board or simulator to use. See section The UDI protocol for AMD29K.
target amd-eb dev speed PROG
-
Remote PC-resident AMD EB29K board, attached over serial lines.
dev is the serial device, as for
target remote
;
speed allows you to specify the linespeed; and PROG is the
name of the program to be debugged, as it appears to DOS on the PC.
See section The EBMON protocol for AMD29K.
target hms
-
A Hitachi SH, H8/300, or H8/500 board, attached via serial line to your host.
Use special commands
device
and speed
to control the serial
line and the communications speed used.
See section GDB and Hitachi Microprocessors.
target nindy devicename
-
An Intel 960 board controlled by a Nindy Monitor. devicename is
the name of the serial device to use for the connection, e.g.
`/dev/ttya'. See section GDB with a remote i960 (Nindy).
target st2000 dev speed
-
A Tandem ST2000 phone switch, running Tandem's STDBUG protocol. dev
is the name of the device attached to the ST2000 serial line;
speed is the communication line speed. The arguments are not used
if GDB is configured to connect to the ST2000 using TCP or Telnet.
See section GDB with a Tandem ST2000.
target vxworks machinename
-
A VxWorks system, attached via TCP/IP. The argument machinename
is the target system's machine name or IP address.
See section GDB and VxWorks.
Different targets are available on different configurations of GDB; your
configuration may have more or fewer targets.
Go to the previous, next section.