Explanation of deet commands
deet_open target args
Start debug session with target program & args
deet_close
Closes the current target program
deet_breakpoint
Sets, removes or lists breakpoints.
deet_continue
Resumes execution
deet_frame
Gets or sets the current stack frame
deet_sym
Looks up a symbol name in the symbol table.
Returns a type id and a value id.
deet_type
Gets type information from a type id.
deet_getval
Gets the value of a given value id represented
as a type id.
Anticipated changes to deet commands:
- deet_open will return an identifier, to be given as the first parameter in other routines. This way, it will be possible to use multiple processes and threads.
- deet_getval will be replaced with deet_val which also writes -OR- deet_putval will be added.
- deet_open will take a parameter which is a command to be executed when an event occurs. Events include: breakpoints, exceptions, new threads.
Gdb Nub notes:
To see input/output from gdb, edit the file gdb_nub/gdbNub.tcl
and change the first line in gdbInit() to set gdbInfo(debug) to 1.
When this flag is set, a window will come up (initially iconified)
showing debugging output from the gdb nub.
Gdb gets a list of source files using the "info sources" command.
On some systems, this can print out a huge list of files. If that
is the case, comment out that line in gdbSym.tcl
- Orgainization
control.tcl:Routines related to starting/stopping a program,
breakpoints, etc.
stack.tcl:Routines for reading stack frames and drawing the
stack window.
sym.tcl:Routines dealing with the symbol table.
window.tcl:Routines that implement the main window and user
interaction.
start.tcl:The script that is initially read to start up the
debugger.
widgets.tcl:A (rather poor) generic widget library I've
implemeted to make some things a little easier.
Includes procedures for hierarchical lists, file
browsers, menus, etc.
init.tcl:A replacement for $tcl_library/init.tcl that will
allow deet to be used interactively.