Tornado

Tornado 2.0
User’s Guide
Use the -B option to select an alternative back end.
If the target agent is connected through the wdbserial back end, target server options -d
and -b allow the tty device and the serial line speed to be specified, respectively. The -hfc
option activates hardware flow control on the serial link.
If the target agent is connected through the wdbrpc backend, the -p option allows to
specify the UDP port number.
If the communication link between the target server and the target agent is slow, it may be
necessary to adjust the back end timeout value (with the -Bt option), as well as the backend
retry count (with the -Br option).
Back ends may also provide their own set of options (see Tornado API Programmer’s Guide
for details). The back end options are shown first. These options can be viewed with:
tgtsvr -B bkendName -h
The WDB requests can be logged on a file by using the -Bd option. The default behavior is
to append log messages at the end of the log file (if it does not exists, it will be created). If
the -Bm option is also specified, the file size will be limited to the given value, and written
as a circular file: i.e. when this value is reached, the file is rewritten from the beginning. If
the file exists, it will be erased.
Object Module Management
The target server may handle object modules from various format (currently, a.out COFF,
ELF, SOM, and pecoff). The core file is analyzed in order to determine what object module
format will be used for the working session. It is possible to bypass this determination
with the -f option followed by a format name. Supported format names can be found in
the resource file: $WIND_BASE/host/resource/target/architecturedb. The target server can
be extended to support new Object Module Format (see the Tornado API Programmer’s
Guide: Object Module Loader).
Target Symbol Table
The target server maintains (on the host) a symbol table for the target executable. It builds
this symbol table from an input file called the core file. The symbols and memory locations
obtained from this file are used to calculate relocation information when linking other
user modules. The target server normally obtains the location of the core file from the
target agent (in which case it is the file originally used as the executable for the agent
itself). However, because the core file may no longer be in the location where it was used
to load the agent, a path name for it can also be specified explicitly with the -c option (see
Locating the Target Executable above for giving an alternate path name).
It is also possible to prevent the target server from building the target symbol table from
the core file with the -N option. If the target server is started with this option, the first file
to be loaded must be a fully-linked object file (an object file with no external references).
Any subsequent modules loaded may be relocatable; the server calculates relocation
information by reference to that first loaded object file.
358