Tornado

Tornado 2.0
User’s Guide
You can prevent CrossWind from looking for the two .gdbinit files, if you choose,
by setting the internal GDB parameter inhibit-gdbinit to yes. Because the
initialization files execute in the order they are listed above, you have the
opportunity to set this parameter before the debugger reads either .gdbinit file. To
do this, insert the following line in your ~/.wind/gdb.tcl:
gdb set inhibit-gdbinit yes
7.7.2 Tcl: Passing Control between the Two CrossWind Interpreters
You can use the following specialized Tcl commands to pass control between the
two CrossWind Tcl interpreters.
uptcl
From the Tcl interpreter integrated with the GDB command parser, uptcl
executes the remainder of the line in the CrossWind graphical-interface Tcl
interpreter. uptcl does not return a result.
downtcl
From the graphical-interface layer, downtcl executes the remainder of the line
in the Tcl interpreter integrated with GDB. The result of downtcl is whatever
GDB output the command generates. Use downtcl rather than ttySend if your
goal is to capture the result for presentation in the graphical layer.
ttySend
From the graphical-interface layer, ttySend passes its string argument to GDB,
exactly as if you had typed the argument in the command panel. A newline is
not assumed; if you are writing a command and want it to be executed, include
the newline character (\n) at the end of the string. Use ttySend rather than
downtcl if your goal is to make information appear in the command panel
(this can be useful for providing information to other GDB prompts besides
the command prompt).
The major use of uptcl is to experiment with customizing or extending the
graphical interface. For example, if you have a file myXWind containing
experimental Tcl code for extending the interface, you can try it out by entering the
following in the command panel:
(gdb) tcl uptcl source myXWind
By contrast, downtcl and ttySend are likely to be embedded in Tcl procedures,
because (in conjunction with the commands discussed in 7.6.3 Tcl: Invoking GDB
Facilities, p.268) they are the path to debugger functionality from the graphical
front end.
274