Version 6 of Dynamic Debugger

Updated 2004-02-12 18:56:23

A sub-category of Category Debugging.

Dynamic debuggers are a strange breed. For whatever reason, many programmers are either unfamilar or dissatisfied with most of the products in this category.

A dynamic debugger allows a developers the controlled execution of some application, stopping it at chosen breakpoints, or when some specific data was changed (watchpoints), doing step-by-step execution, examining the contents of callstacks, variables, and the like.

Any dynamic debugger having its own page should have a link to this page on its page, like for normal categories. That way clicking on the title of this page will then deliver a list of tools in this sub-category.

The list of options below is only for external references we cannot categorize directly, and unnamed tools which are part of greater system. The moment such tools get their own page here they will be removed from the list below and can be reached through the title of this page. --- Not yet, work in progress ---


  • http://www.codeforge.com/ has an IDE which supports Tcl as well as several other languages. Commercial.
  • Juice [L1 ] is a Tcl 8.0 debugger with GUI interface. Link not found!
  • MyrmecoX by NeatWare is a commercial Tcl debugger for Windows. It is based on the open TclPro sources.
  • The Tcl Dev Kit by ActiveState is also based upon TclPro, with a number of enhancements. Relevant in this section is prodebug, a visual debugger with breakpoints, watchpoints, code coverage analysis, sourcecode viewing, etc. The latter part integrates with procheck to show static syntax errors while stepping through the application. Commercial.
  • Tcl Debug [L2 ] is a dynamically loadable extension written by Don Libes which provides breakpoints and single stepping of a Tcl script. Tom Tromey has extended this extension to provide filename and line number associations with statements.
  • Tdb [L3 ] is a debugger for Tcl scripts.
  • TIDE [L4 ] is an integrated development environment including version control management interfaces, debugger interface, difference/merge into version control management system tool, smart editing, simple project management, call tree browser, variable usage tracking, and ability to generate byte codes or stand alone binaries. It is a commercial product and makes use of the ICE compiler.
  • tk-debug [L5 ] is a Tk interacter for Don Libes' Tcl Debug.
  • Tuba [L6 ] is a Tcl/Tk 8 debugger with breakpoints, source code viewing, watchpoints, etc. Download from http://www.eolas.net/tcl/tcl-tuba25b1.zip viz. http://www.eolas.net/tcl/tcl-tuba24p1.zip Notice that tuba served as "a base for TclPro ..."
  • Komodo by ActiveState is a graphical editor and code debugging environment for several languages, including Tcl.
  • Another alternative here is to make use of your system's C level debugger - say gdb, codecenter, whatever... to start up the interpreter. Then once it is up, start up your tcl debugger, or tkcon, etc. so that you can see what your program will see AND see what is going on under the covers so to speak.
  • Not to mention the fun one could have with a tcl-level debugger which is able to interface to a tcl-aware C level debugger like SmartGDB [L7 ]. Of course, this makes sense only if Tcl-level debugger (interface) and debugged application do not share the same process, i.e. they have to talk via pipes or sockets with each other. -- AK
  • Insight aka gdbtk [L8 ] by Cygnus merges gdb and Tcl/Tk. The idea from the last point applies here too.
  • Testcov (test coverage) is a tool to register which parts of the code have been executed how often, it is less than perfect but it does a fairly nice job. Soon available on ProcPlace's archive. Arjen Markus
  • atkdebugger is a debugger extension that is fully integrated into Xotclide. It adds almost everything that this debugger needs. (no performance loss, no reparsing).
  • RamDebugger is a graphical debugger for Tcl/Tk developed in Tcl/Tk.

[ Category Debugging ]