Deet Version 1.0a - 3/30/97 ---------------------------- This is the first alpha release of Deet. It is therefore incomplete and not thoroughly tested. Use at your own risk. See the license.terms file for licensing information. What is Deet? ---------------------------- Deet is a graphical debugger that is intended to be easily retargetted to different languages, compilers, operating systems, etc. It does so by separating core debugger functionality from user interface. All debugger functionality is implemented with the deet_* commands, explained in README.devel. Included with this release of deet is a C debugger written as a layer on top of gdb. Other instantiations are planned for Java, Microsoft C++ and Tcl. Deet should work with wish4.0 and greater, although wish4.1 and up is recommended. Installation ---------------------------- Edit the Makefile and set the indicated variables as appropriate for your system. "make" will compile a small program to allow control of the terminal for interactive programs and generate a script for the deet executable. "make install" will copy files to the directories indicated in the Makefile. Documentation ---------------------------- There is no documentation with this release other than this README and README.devel (which contains notes for those interested in modifying or extending deet). Upcoming releases will have a man page and user documentation. See also http://www.cs.princeton.edu/~jlk/deet for more info, including a USENIX paper on deet. Running Deet ---------------------------- Usage: deet [target name and arguments] (gdb must be in your path) To try deet on a sample program: cd test make ../deet simplehash -or- ../deet "./wf < input" Bugs ---------------------------- One major bug so far is that the target must have already hit a breakpoint in order for interrupting execution to work. You cannot stop a running program at all if you are using wish4.0. Please report all bugs/suggestions/comments to me: Jeffrey Korn jlk@cs.princeton.edu