Conversations over the years have shown me that DDD was a great inverse marketing tool, ironically pushing developers towards the embedded debugger UI in their favorite IDEs... despite DDD itself being indeed very powerful. But even "usefulness over aesthetics" has its limits!
I've found it a very powerful yet compact way to visualize the state of a program when debugging.
A while ago there was a project to port it to GTK3 but I think that went away. I'm glad the mainline project is still going.
Absolutely. I wrote about its features here https://begriffs.com/posts/2022-07-17-debugging-gdb-ddd.html
Since the article was written, the maintainers fixed the issues I pointed out. No need for many of those workarounds now. Versions 3.4.0 and 3.4.1 are substantial.
The DDD website ( https://www.gnu.org/software/ddd/ ) points to the source tar.gz and the full manual, but nothing that says "What's New" in recent versions.
There was even a story, that (at least for Common Lisp), you can start from almost blank state, but have an exception handler installed (that can continue), so as you go you live-edit and add pieces missing, or if code crashes change.
This is all good, until nowadays, where you really want to know what's deployed in production, and not just the last stuff I've live fixed.
I mean, I guess both have values tbh, but hard to pull two models like this and use... bit like - debugger or printf statements (or both!)
¹ https://www.gnu.org/prep/standards/standards.html#NEWS-File
² https://svn.savannah.gnu.org/viewvc/ddd/trunk/doc/NEWS?view=...