Debugging TclUse Komodo to debug Tcl programs locally or remotely. See below for instructions on configuring Komodo to debug Tcl programs. For general information about using the Komodo debugger, see Komodo Debugger Functions. Note: in order to debug Tcl programs, you must have ActiveState's Tcl Dev Kit, available with a membership to ASPN Tcl. Configuring the Tcl DebuggerYou must specify which Tcl interpreter Komodo should use to debug and run Tcl programs. To specify the Tcl interpreter:
If no Tcl interpreter is displayed in the list, ensure that the location of
the interpreter is specified in your system's ![]() Using the Tcl Remote DebuggerKomodo's Remote Debugger is used to open a program on another machine and debug the program using Komodo. In order to use Komodo's remote debugger, you must first install the Tcl Remote Debugger programs on the remote machine, which call the machine running Komodo. Then you use the Komodo debugger on your local machine to debug your remote program. Note: in order to remotely debug Tcl programs, you must have ActiveState's Tcl Dev Kit, available with a membership to ASPN Tcl, installed on the remote machine. ASPN Tcl memberships will be available in December 2001. Installing the Tcl Remote Debugger on the Remote MachineThe Tcl Remote Debugger is a collection of Tcl files that need to
be installed on the remote machine. These files were installed in
the To install the Tcl Remote Debugger:
![]() Invoking the Tcl Remote DebuggerTo debug a Tcl script on a remote machine:
For example, consider the following scenario: Remote Machine In this scenario, you would enter the following command on the remote machine: tclsh /remote_debug/tdbg.tcl -file test.tcl -port-komodo 9000 -host-komodo mybox
Once the connection is established, you can use the full Komodo debugging functionality, including setting breakpoints, stepping, viewing the call stack, and watching variables. The output from the debug process appears in the Output pane in the Komodo Workspace. To stop the debugger:
![]()
|