Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] dbx debugger support in CDT

Elena Laskavaia wrote:
Yes it does work approximately this way.
If you really starting from the scratch and your debugger is not like gdb you can start with debug tutorial and small project they used (for artificial assembly language). Search for debugger tutorial on EclipseCon 2008.

To clarify a bit more, there are actually two versions of this tutorial. One uses the standard debug model from platform and is covered by at article ( The other uses the same language and interpreter and is based on DSF. This one was presented at the 2008 EcliseCon tutorial ( As the co-author of the DSF framework I can't really be impartial in which to recommend for you, but it really depends on your needs. The standard debug model has been around a long time and is quite mature and there are lots of examples in using it. DSF is still evolving and is more focused on performance and features related to remote (embedded) debugging. BTW, the DSF-based example has evolved a little since the tutorial and now supports multi-threading.


More complex would be gdb mi implementation that is currently developed by DSF guys, this is still much simpler than current gdb/mi/cdi mess in CDT.

Achim Bursian wrote:
Ah well, maybe I should add, I read all of the thread "Question on future debugger interface", by Rick Moseley.
So don't simply point me there :-)

Still, all these TCF, DSF, MI etc. acronyms are quite confusing for a newcomer :-(

I thought it would be as "easy" as launching a dbx process and then "talking" to that as if I were a human (sending commands, and parsing the textual results that dbx prints to stdout). Doesn't it work that way at all?


cdt-dev mailing list
cdt-dev mailing list

Back to the top