ddd API?

[R. Bernstein]

As someone who added two debugger front ends (for Bash, and GNU make)
and has been hacking away at the Python debugger front end, I am not
aware of any such document. Worse, things are not really consolidated
in just a few files, but are rather spread out over maybe 5-10 files.

One way to get a a list of files that need to be changed might be to
compare ddd-3.3.11 with ddd-3.3.12-test2 (the version that's in the
files section of the bashdb project:
http://sourceforge.net/project/showfiles.php?group_id=61395&package_id=65341
not what's in CVS that's *also* called test2). The changes between
ddd-3.3.11 and that 3.3.12 are just those to add a frontend for the
GNU make debugger.

Loking at the differences you'll se not only the files but you may
also be able to glean what specific parts of those files need to be
changed.

In general the process I use is for this feature (e.g. how to issue a
debugger "step" command) language R is like language Y so see have ddd
handle it like Y here.

For example, bash has variable interpolation like Perl, so use that
there. And like Perl, but not like gdb, when you start up you are
already somewhere inside the program to be debugged). The bash
debugger shows tracebacks like gdb, so follow that in the portion that
deals with tracebacks. In fact the bash debugger has many commands
like gdb, so you will see many switch statements where case gdb will
be shared with the case for bashdb as well.

Good luck!


Duncan Murdoch writes:
 > Is there a developer page or document somewhere describing what's 
 > necessary to add support for a new debugger to ddd?  I'd like to use ddd 
 > as a front-end when debugging R (www.r-project.org); it's an interpreted 
 > language.
 > 
 > Duncan Murdoch
 > 
 > 
 > _______________________________________________
 > Ddd mailing list
 > address@hidden
 > http://lists.gnu.org/mailman/listinfo/ddd
 >