Eclipse C/C++ Development Tooling (CDT) 9.2.0 Release Review

End Date of the Review Period: 

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Wednesday, December 7, 2016



CDT 9.2 is a small feature release that brings a couple of nice new feature to our users as well as bug fixes.  

The feature of most visibility is a tight integration between CDT and a command-line use of GDB (GNU Debugger). Users can now control GDB through its standard command-line interrface from within Eclipse (just as if they had started it from command shell), while CDT stays synchronized and provides the full-fledge IDE benefits.  This GDB console, as well as the legacy one (which is still used for older GDBs) have been moved to new view called "Debugger Console".

The new Core Build architecture is in place that links launch targets provided by the Launch Bar with build configurations automatically. Qt and CMake support are added based on this architecture joining the Arduino C++ support that was the proving ground for this architecture. The Qt feature is marked as Preview, the CMake feature as Experimental, while the Arduino C++ feature graduates from Preview to full GA.




API Certification: 

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues: 

CDT 9.2 introduces a full-features GDB console which allows users to control GDB fully using a command-line interface.  We anticipate that users will want to have access to that full GDB console while still wanting to see the output of the program being debugged.  Although this can be achieved using the Pin/Clone paradigm of the platform console view, we felt the paradigm was non-obvious.  Therefore, we have de-coupled the GDB console from the program console by creating a new Debugger Console view.  The new full GDB console, as well as the legacy GDB console (still used for older GDB versions) are both being displayed in this new Debugger Console view.  

The new view does not have the same extensibility features provided by the platform Console view.  Although this is a limitation, it was felt it was worth the impact.  We hope to improve the extensibility of the new view in future releases.

Security Issues: 

No known security issues.

Non-Code Aspects: 

User documentation is being updated sporadically.  However, with internet searches, the value of the documentation is reduced.


Usability Details: 

This release improve usability by:

  • providing a new Debugger Console view decoupled from the platform Console view
  • hiding the 'gdb traces' by default
End of Life: 

APIs that should no longer be used are marked as deprecated as the situation dictates.


The community implication seems to be slightly reduced.  A handful of committers stand-out as being very active and drive the majority of the progress of the project.