| Re: [cdt-dev] dbx debugger support in CDT |
Achim Bursian wrote:
I'm not entirely sure what you have in mind by "CDT will use that"? With debuggers, the case is more that debugger uses CDT and not so much the other way around. There are a few CDT-specific features such as disassembly, breakpoints, various variables views' actions which are in CDT and if you would like to use those you will need to do some work to implement the APIs that they require. If it is important for you to use these CDT features then I would recommend that you do use either the DSF or CDI framework. CDI is also an older framework which implements the standard debug model and allows you to implement a lower-level API (known as CDI). These frameworks do a lot of the work to integrate with the above mentioned CDT features and would save you some work. I don't think there is a tutorial for implementing a debugger based on CDI, so the GDB reference implementation is your best guide.Pawel Piech wrote: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 (http://www.eclipse.org/articles/Article-Debugger/how-to.html). The other uses the same language and interpreter and is based on DSF. This one was presented at the 2008 EcliseCon tutorial (http://www.eclipsecon.org/2008/?page=sub/&id=44).So does this mean that CDT could run with both versions? At least the first approach is absolutely not related to CDT. If I simply create a debugging plugin with the standard debug model from platform, CDT will use that? Or is there any special handling necessary for CDT, like glue code etc.?
Cheers, Pawel
Our needs are basically to get a running dbx integration pretty fast, and it should be stable. It doesn't need everything a debugger has (like special registers of the CPU), more the basic stuff: Breakpoints, stepping, variable display and watches. If there is a special problem that can't be solved that way, we could still fall back to our old debugger (although that is not what we want, of course). For dbx, remote debugging is no point for us. dbx is used only to debug on the same machine, and it is needed because we use the SunStudio sparc compiler, which produced debug info that is not usable by gdb.Cheers, Achim _______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev