My only feeback on this announcement is that I think the DDD debugger is
fabulous for C++ debugging, but it can't seem to hack it with java...
atleast not the multithreaded work I've been dealing with.
I've been using JDB for java debugging because it has nice multithreading
debugging support. Also, I've been using traces quite a bit.
However, the advantage I see in using something like DDD is simply
analyzing program behavior. Being able to mouse-over variables.... being
able to display complex data structures... it's all really time effective
for understanding how foreign code operates without studying it for hours.
I could do without the graphics, but it would be nice to support some
complex routines for inspecting data that go beyond printing a single
variable's value. In that respect, it might even be nice to make this an
extensible debugger with a console.
This is a big wish here, and an idea I've had for a while about debuggers.
In my meager rumblings with program efficiency, I've thought it would be
cool for debuggers to output profiling information. In other words, when
you "next" it could give the time the statement took to execute.
But these are demanding projects. My real hope is just to be able to use
something other than JDB with good useability.
-Bill
