target type parameters
targetcommand does not repeat if you press RET again after executing the command.
info files(see section Commands to specify files).
help target name
set gnutarget args
set gnutargetcommand. Unlike most
targetrefers to a program, not a machine. Warning: To specify a file format with
set gnutarget, you must know the actual BFD name. See section Commands to specify files.
show gnutargetcommand to display what file format
gnutargetis set to read. If you have not set
gnutarget, GDB will determine the file format for each file automatically, and
show gnutargetdisplays `The current BDF target is "auto"'.
Here are some common targets (available, or not, depending on the GDB configuration):
target exec program
target core filename
target remote dev
target remotenow supports the
loadcommand. This is only useful if you have some other way of getting the stub to the target system, and you can put it somewhere in memory where it won't get clobbered by the download.
The following targets are all CPU-specific, and only available for specific configurations.
target abug dev
target adapt dev
target amd-eb dev speed PROG
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 array dev
target bug dev
target cpu32bug dev
target dbug dev
target ddb dev
target dink32 dev
target e7000 dev
target es1800 dev
target est dev
target hms dev
speedto control the serial line and the communications speed used. See section GDB and Hitachi microprocessors.
target lsi dev
target m32r dev
target mips dev
target mon960 dev
target nindy devicename
target nrom dev
target op50n dev
target pmon dev
target ppcbug dev
target ppcbug1 dev
target r3900 dev
target rdi dev
target rdp dev
target rom68k dev
target rombug dev
target sds dev
target sparclite dev
target sh3 dev
target sh3e dev
target st2000 dev speed
target udi keyword
target vxworks machinename
target w89k dev
Different targets are available on different configurations of GDB; your configuration may have more or fewer targets.
Many remote targets require you to download the executable's code once you've successfully established a connection.
loadcommand may be available. Where it exists, it is meant to make filename (an executable) available for debugging on the remote system--by downloading, or dynamic linking, for example.
loadalso records the filename symbol table in GDB, like the
add-symbol-filecommand. If your GDB does not have a
loadcommand, attempting to execute it gets the error message "
You can't do that when your target is ..." The file is loaded at whatever address is specified in the executable. For some object file formats, you can specify the load address when you link the program; for other formats, like a.out, the object file format specifies a fixed address. On VxWorks,
loadlinks filename dynamically on the current target system as well as adding its symbols in GDB. With the Nindy interface to an Intel 960 board,
loaddownloads filename to the 960 as well as adding its symbols in GDB. When you select remote debugging to a Hitachi SH, H8/300, or H8/500 board (see section GDB and Hitachi microprocessors), the
loadcommand downloads your program to the Hitachi board and also opens it as the current executable target for GDB on your host (like the
loaddoes not repeat if you press RET again after using it.
Go to the first, previous, next, last section, table of contents.