Debugging with GDB Manual (5900-1473; WDB 6.2; January 2011)

transfer is also limited by the size of the target
packet and the memory cache.
show download-write-size Displays the current value of the write size.
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 (for example, /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 will not get clobbered by the download.
target sim Builtin CPU simulator. GDB includes simulators for most
architectures. In general,the following commands work:
target sim
load
run
However, you cannot assume that a specific memory
map, device drivers, or even basic I/O is available,
although some simulators do provide these.
Some configurations may include these targets as well:
target nrom dev NetROM ROM emulator. This
target only supports
downloading.
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 code once you have
successfully established a connection.
load filename Depending on what remote debugging facilities are configured
into GDB, the load command 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
128 Specifying a Debugging Target