1. TDB
Ted may also run in debugger mode when run with the program name tdb.
TDB acts as a debugger frontend for gdb and weld.
TDB can display complex views into program data while debugging.
And of course, you can edit as well:
TDB is a light-weight debugger-frontend, editor and IDE whose goal is to simplify the edit/build/debug cycle of application development. TDB itself is implemented entirely in Tcl/Tk and is builtin to the Ted editor.
TDB can navigate through warning and error messages from gcc, make, and/or Weld. It places the editor at the offending file and line. When a build is satisfied, TDB can run the program in the debugger, allowing single stepping, viewing/modifying variables and moving up and down call-stacks. Break and watchpoints are also supported as are drill-down displaying of complex data.
TDB displays data in the top window, the text source in the middle, and commands and output below. Double-clicking in the edit window toggles breakpoints. Variables under the mouse pointer are printed automatically. Or you may highlight a variable, and click Print or Display.
While debugging, the current line is shown highlighted in blue. Breakpoints are in red, or orange if they are also the current line.
TDB has a simple project style interface, but currently this is used mostly to generate a makefile.
TDB will also use tag files generated by ctags, supporting lookups of symbols.
All gdb commands are available directly via the command/display window. Or use, Auto-next to animate-execute your program, hitting Escape to stop. To start TDB, use "./tdb a.out" on unix or "wish84 tdb a.exe" on Windows. After the file name, you may optionally give a process id to attach to, or "core" for a core file to read.
TDB also will take parameters on the command line to pass to the program at startup by using a -- to indicate begin of program parms. For example:
tdb a.out -- -test 1 -debug 5
© 2008 Peter MacDonald