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.
target command does not repeat if you press <RET> again
after executing the command.
info files(see Commands to Specify Files).
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 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 BFD target is "auto"’.
Here are some common targets (available, or not, depending on the GDB configuration):
For example, if you have a board connected to /dev/ttya on the machine running gdb, you could say:
target remote /dev/ttya
target remote supports the
load command. 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.
target sim load run
works; however, you cannot assume that a specific memory map, device
drivers, or even basic I/O is available, although some simulators do
provide these. For info about any processor-specific simulator details,
see the appropriate section in Embedded Processors.
runcommand spawn native processes (likewise
attach, etc.) even when
off(see set auto-connect-native-target).
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. You may wish to control various aspects of this process.
set debug monitor
show debug monitor
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
If your gdb does not have a
load command, 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.
It is also possible to tell gdb to load the executable file at a specific offset described by the optional argument offset. When offset is provided, filename must also be provided.
Depending on the remote side capabilities, gdb may be able to load programs into flash memory.
load does not repeat if you press <RET> again after using it.