02.03.2014 Views

Tornado

Tornado

Tornado

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

C<br />

<strong>Tornado</strong> Tools Reference<br />

Using the -A option forces the target server to include all global and local symbols from<br />

the core file in the target server symbol table.<br />

Target Memory Management<br />

The target server manages the target agent memory pool on the remote system. This<br />

memory pool is mainly used by the loader when object files are downloaded. The target<br />

server automatically increases the size of the agent memory pool when necessary (when<br />

there is not enough room to load a file, for example). A cache is implemented so that<br />

memory-related requests from <strong>Tornado</strong> tools may be satisfied at the target server level,<br />

avoiding the transfer of data from the real target memory. This cache has a default<br />

maximum size of 1 MB.<br />

The -m option allows to specify a maximum size for the cache. This may be required when<br />

the agent memory pool size becomes greater than the maximum size of the cache. In this<br />

situation, the memory-related requests that fall outside the cache are satisfied at the target<br />

level, and thus are substantially slower.<br />

The <strong>Tornado</strong> browser provides a graphical view of the target agent memory pool<br />

utilization.<br />

C<br />

Virtual Input/Output Mechanism<br />

The target server can redirect data through virtual Input/Output channels. For target tasks<br />

to have access to this mechanism, a Virtual I/O Driver must be included in the target<br />

system. When this driver is included, any task on the target may open a virtual channel to<br />

read from, or write to, that channel. On the host, any tool may open the same virtual<br />

channel to write to, or read from, that channel. Thus the target server acts as an I/O<br />

dispatcher, multiplexing whatever physical communications layer is available to allow<br />

run-time tasks and host tools to communicate easily.<br />

When the target server is started with the -C option, a console window attached to virtual<br />

channel 0 is displayed. On UNIX, this window can be displayed on a specified X server<br />

(including a host other than where the target server is running) with the -display option.<br />

The number of buffered lines (default 88) can be changed by setting the environment<br />

variable WTX_CONSOLE_LINES to the number of desired buffered line. Set this variable<br />

before starting your UNIX target server.<br />

This permits any task on the target to open virtual I/O channel 0 to send characters to, or<br />

read characters from, this window. If started with -redirectIO, a redirection of target<br />

standard I/O is automatically done. If -redirectIO is set, but -C flag is not set, the target<br />

I/O will be redirected to the target server, but, since no console will be present to display<br />

the informations, events will be sent to the connected WTX tools.<br />

The target server can also be used as a virtual target shell console: The shell is running on<br />

the target, and its I/O are done from the target server virtual console. To do this, use the -<br />

redirectShell flag in conjunction with -C flag. The target server will automatically redirect<br />

the target shell I/O into the default target server console. The shell must be included in<br />

the target system. This feature is useful if target is only accessible through back end and<br />

359

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!