Commands for managing targets

target type parameters

Connects the 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.

set gnutarget args

uses its own library BFD to read your files. knows whether it is reading an executable, a core, or a .o file, however you can specify the file format with the set gnutarget command. Unlike most target commands, with gnutarget the target refers 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 gnutarget

Use the show gnutarget command to display what file format gnutarget is set to read. If you have not set gnutarget, will determine the file format for each file automatically and show gnutarget displays The current BDF target is "auto".

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 cpu32bug dev

CPU32BUG monitor, running on a CPU32 (M68K) board.

target op50n dev

OP50N monitor, running on an OKI HPPA board.

target w89k dev

W89K monitor, running on a Winbond HPPA board.

target est dev

EST-300 ICE monitor, running on a CPU32 (M68K) board.

target rom68k dev

ROM 68K monitor, running on an IDP board.

target array dev

Array Tech LSI33K RAID controller board.

target sparclite dev

Fujitsu sparclite boards, used only for the purpose of loading. You must use an additional command to debug the program. For example: target remote dev using standard remote protocol.

Choosing target byte order

You can now choose which byte order to use with a target system. Use the set endian big and set endian little commands. Use the set endian auto command to instruct to use the byte order associated with the executable. You can see the current setting for byte order with the show endian command. Warning: Currently, only embedded MIPS configurations support dynamic selection of target byte order.

Go to the first, previous, next, last section, table of contents.