Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CDI Debugger will be REMOVED in CDT 9.0/Neon

Just for the records, the TCF Debugger is based on plain Platform/Debug , and we found this to be sufficient to be successful.

 

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Bruno Medeiros
Sent: Wednesday, August 12, 2015 7:47 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] CDI Debugger will be REMOVED in CDT 9.0/Neon

 

Note: I wasn't talking about refactoring DSF or DSF-GDB themselves, but rather refactor CDT Core and UI to pick out utils and other common code into separate plugins. Ideally this would be a superficial refactoring - just moving a few classes around, maybe a few methods - but in practice I reckon it wouldn't be that simple, there be more in-depth refactoring required. (I haven't looked into it in detail) I might give it a go if I have the time.

As for refactoring DSF itself, I agree with Mark, things are actually pretty decent at the moment. Even if DSF doesn't work very well for implementing a new debugger integration (that isn't GDB nor MI-based), at least it still gives us DSF-GDB, which is quite nice.

 

Sure, there are a few things I'd like to see in DSF-GDB that make the handling of non-C/C++ languages better. But if I look at the big picture, it's actually in GDB itself that a lot of limitations come from, so that is a stress point much more than DSF-GDB is...

 

This does pose an interesting question: if someone where to write say, native LLDB integration for CDT, would they be better off using DSF as a base, or writing a debugger integration from scratch (just Platform Debug)...

 

 

On Wed, Aug 12, 2015 at 3:31 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:

You need to be careful about what part of DSF you want to refactor. The original intent was that the general framework could be pushed down to the Platform Debug. That could still be possible with some refactoring I assume.

 

For the more general gdb/C++ debugging case, we should consider ways to improve the debug experience by leveraging the knowledge that the CDT core has about the code in the projects and about what toolchain is being used to build those projects, which generally determine which debugger you want to use with DSF.

 

But I’ll say this, I’m not sure DSF is the right framework for debugger integration to begin with. It does more, like handle the flexible hierarchy, and CDI can’t do that. But there’s way too much magic behind DSF, to quote Uncle Bob (http://blog.cleancoder.com/uncle-bob/2015/08/06/LetTheMagicDie.html). We really need to ask ourselves if we really need all that magic.

 

As I have great success redoing the build system to a simpler model, I imagine we could do the same with debug at some point. And while doing that, we need to make sure we can handle many different languages, not just C and C++ but all the ones that Bruno works with and the entire Clang and gcc family as well.

 

Doug.

 

 

From: <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Wednesday, August 12, 2015 at 9:50 AM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>


Subject: Re: [cdt-dev] CDI Debugger will be REMOVED in CDT 9.0/Neon

 

If someone is willing to do the necessary changes to remove those dependencies, then yes, CDT 9.0 is the ideal opportunity.

Marc


From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Bruno Medeiros [bruno.do.medeiros@xxxxxxxxx]
Sent: August 12, 2015 8:58 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] CDI Debugger will be REMOVED in CDT 9.0/Neon

While we're on the subject, any chance to improve the plugin dependencies that the CDT DSF debugger has on the Core and UI CDT plugins? (that is, remove them to only the minimum required - likely requiring refactoring to a CDT commons plugin)

This is a throwback to https://bugs.eclipse.org/bugs/show_bug.cgi?id=421166 . It might also help make the Standalone debugger a bit leaner?

 

On Tue, Jul 14, 2015 at 7:25 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:

Hello,

extenders should be aware that the CDI Debugger will be removed from the CDT code base
as part of the CDT 9.0/Neon release.

Anyone still based on CDI should migrate to DSF before then if they want to continue to compile
with the latest CDT. 

Such a migration has been done by many over the last few years.
The CDT community should be a good resource to get this done for those that may be
finding it difficult.  Searching this mailing list will surely provide some good pointers.

CDT of course provides the DSF-GDB integration which is a very rich example, as well
as an example plugin that extends DSF-GDB itself, for those that use GDB/MI.


Marc


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev




--


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev




--


Back to the top