Tornado

7
Debugger
■
Shell Commands
You can run any of the WindSh primitive facilities described in 5.2.3 Invoking
Built-In Shell Routines, p.156 in the command panel, by inserting the prefix
“wind-” before the shell command name. For example, to run the shell td( )
command from the debugger, enter wind-td in the command panel.
Because of GDB naming conventions, mixed-case command names cannot be
used; if the shell command you need has upper case characters, use lower case
and insert a hyphen before the capital letter. For example, to run the
semShow( ) command, enter wind-sem-show.
7
! CAUTION: The debugger does not include the shell’s C interpreter; thus, the
“wind-” commands are interfaces only to the underlying Tcl implementations
of the shell primitives. For shell primitives that take no arguments, this makes
no difference; but for shell primitives that require an argument, you must use
the shell Tcl command shSymAddr to translate C symbols to the Tcl form. For
example, to call the shell built-in show()on a semaphore ID mySemID, use the
following:
(gdb) wind-show [shSymAddr mySemId]
■
Server Protocol Requests
The Tornado tools use a protocol called WTX to communicate with the target
server. You can send WTX protocol requests directly from the GDB command
area as well, by using a family of commands beginning with the prefix “wtx-”.
See Tornado API Guide: WTX Protocol for descriptions of WTX protocol
requests. Convert protocol message names to lower case, and use hyphens in
place of underbars; for example, issue the message WTX_CONSOLE_CREATE
as the command wtx-console-create.
Extended Debugger Variables
You can change many details of the debugger’s behavior by using the set
command to establish alternative values for internal parameters. (The show
command displays these values; you can list the full set interactively with help
set.)
The following additional set/show parameters are available in CrossWind beyond
those described in GDB User’s Guide:
259