Tornado

7
Debugger
(gdb) tclproc mld mload
This command creates a new GDB command, mld. Now, instead of typing tcl
mload, you can run mld as follows:
(gdb) mld vxColor.o priTst.o
You can collect Tcl procedures in a file, and load them into the GDB Tcl interpreter
with this command:
(gdb) tcl source tclFile
If you develop a collection of Tcl procedures that you want to make available
automatically in all your debugging sessions, write them in the file .wind/gdb.tcl
under your home directory. The GDB Tcl interpreter reads this file when it begins
executing. (See 7.7.1 Tcl: Debugger Initialization Files, p.273 for a discussion of how
all the CrossWind and GDB initialization files interact.)
7
7.6.2 Tcl: Specialized GDB Commands
The CrossWind version of GDB includes four commands to help you use Tcl. The
first two were discussed in the previous section. The commands are:
tcl command
Passes the remainder of the command line to the Tcl interpreter, without
attempting to evaluate any of the text as a GDB command.
tclproc gdbName TclName
Creates a GDB command gdbName that corresponds to a Tcl procedure name
TclName. GDB does not evaluate the arguments when gdbName is invoked; it
passes them to the named Tcl procedure just as they were entered.
NOTE: To execute tclproc commands automatically when GDB begins
executing, you can place them in .gdbinit directly (see GDB Initialization Files,
p.253), because tclproc is a GDB command rather than a Tcl command.
However, if you want to keep the tclproc definition together with supporting
Tcl code, you can exploit the gdb Tcl extension described in 7.6.3 Tcl: Invoking
GDB Facilities, p.268 to call gdb tclproc in ~/.wind/gdb.tcl.
tcldebug
Toggles Tcl debugging mode. Helps debug Tcl scripts that use GDB facilities.
When Tcl debugging is ON, all GDB commands or other GDB queries made by
the Tcl interpreter are printed.
267