Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/User/NewIn90"
(→API modifications) |
(→API modifications) |
||
Line 65: | Line 65: | ||
'''org.eclipse.cdt.dsf.gdb''' | '''org.eclipse.cdt.dsf.gdb''' | ||
+ | # The protected method GdbLaunchDelegate.cleanupLaunch() has been removed. It has been replaced with GdbLaunchDelegate.cleanupLaunch(ILaunch). Although the replaced method was not deprecated, it was used in an incorrect fashion and we felt it was justified to modify it. | ||
# The deprecated protected methods '''GDBBackend.getGDBCommandLine()''' and '''GDBBackend.launchGDBProcess(String)''' were removed. '''GDBBackend.getGDBCommandLineArray()''' and '''GDBBackend.launchGDBProcess(String[])''' should be used instead. | # The deprecated protected methods '''GDBBackend.getGDBCommandLine()''' and '''GDBBackend.launchGDBProcess(String)''' were removed. '''GDBBackend.getGDBCommandLineArray()''' and '''GDBBackend.launchGDBProcess(String[])''' should be used instead. | ||
# The deprecated protected method '''GdbLaunchDelegate.newServiceFactory(String)''' was removed. It was replaced with GdbLaunchDelegate.newServiceFactory(ILaunchConfiguration, String) | # The deprecated protected method '''GdbLaunchDelegate.newServiceFactory(String)''' was removed. It was replaced with GdbLaunchDelegate.newServiceFactory(ILaunchConfiguration, String) |
Revision as of 14:18, 22 February 2016
Contents
General
- Is is now possible to convert an existing C project to a C++ project (adds C++ nature). To do this, the existing wizard 'Convert to a C/C++ project' can now be used on C projects whereas before it could only be used on non-CDT projects.
Editor
- When code completion is invoked in a function call expression, appropriate substitutions are suggested for each of the function parameters. link
- In C++ files if "Type not found" error is detected, there is a new quick fix now to create a class based on that type, which opens "New C/C++ Class Wizard".
Picture: TBD
Makefile Editor
- Makefile Editor now provides a *single* key Ctrl+/ to toggle comments rather than have Ctrl+/ to comment and Ctrl+\ to uncomment. This is consistent with CDT and Java editors. See Bug-485028
Parser
Build
- The "Symbols" settings category (gnu.c.compiler.category.symbols) under "GCC C compiler" has been removed and its content has been merged with the Preprocessor (gnu.c.compiler.category.preprocessor) category. link
Debug
Gdbserver options
- For automatic remote debugging sessions, CDT now supports specifying extra options that will be passed to gdbserver when starting it. This way, users could activate debug messages ("--debug"), benefit of wrapper option ("--wrapper") that gdbserver supports or use the other available command-line options of gdbserver.
Removal of support for the old Apple GDB
Apple used to have their own version of GDB which was released with Xcode. Apple no longer releases their own GDB version, and that since 2013. As of CDT 9.0, the support for the obsolete Apple GDB has been removed. As an alternative, the GDB from the FSF (Free Software Foundation) can be used. Some instructions on how to do this are available on the CDT FAQ page.
OS Resources View
Attach to selected processes
OS Resources view displays different information about the resources of the operating system, such as list of all processes running on the target or files opened by processes on target.
Now it is possible to attach to processes associated with selected resources directly from OS Resources view without resorting to "Connect to a process" button from Debug View.
This feature requires non-stop mode support to be activated.
This feature was completed through Bug 486521.
Copy to clipboard
OS Resources View lists a lot of text information. Now it is possible to copy selected lines to clipboard to save for later comparison.
Bugs Fixed in this Release
See Bugzilla report Bugs Fixed in CDT 9.0
API modifications
With CDT 9.0, some public API are being modified. Below is the list of changes that are not backwards-compatible that extenders could trip on.
org.eclipse.cdt.core
- The deprecated methods ICPPTemplateInstance.getArguments() and ICPPClassTemplatePartialSpecialization.getArguments() were removed. ICPPTemplateInstance.getTemplateArguments() and ICPPClassTemplatePartialSpecialization.getTemplateArguments() should be used instead.
- The deprecated method ICPPSpecialization.getArgumentMap() was removed. ICPPSpecialization.getTemplateParameterMap() should be used instead.
- The deprecated method ICPPTemplateScope.getTemplateDefinition() was removed. ICPPTemplateScope.getTemplateDeclaration() should be used instead.
- The deprecated method INodeFactory.newTranslationUnit() was removed. INodeFactory.newTranslationUnit(IScanner) should be used instead.
org.eclipse.cdt.codan.core https://git.eclipse.org/r/#/c/63810/
- Method IChecker.enabledInContext(IResource resource) was removed. Just remove the implementation since the method is not called.
- Method IProblemLocationFactory.createProblemLocation(IFile file, int startChar, int endChar) was removed. If you implement this interface, remove @Override annotation, if you use this method, replace with createProblemLocation(file, startChar, endChar, -1) (or appropriate line number, note: passing -1 is OK since it will recalculate the line from positions)
- Constructor CodanProblemLocation(IResource, int, int) was removed, use CodanProblemLocation(IResource file, int startChar, int endChar, int line) instead.
org.eclipse.cdt.dsf.gdb
- The protected method GdbLaunchDelegate.cleanupLaunch() has been removed. It has been replaced with GdbLaunchDelegate.cleanupLaunch(ILaunch). Although the replaced method was not deprecated, it was used in an incorrect fashion and we felt it was justified to modify it.
- The deprecated protected methods GDBBackend.getGDBCommandLine() and GDBBackend.launchGDBProcess(String) were removed. GDBBackend.getGDBCommandLineArray() and GDBBackend.launchGDBProcess(String[]) should be used instead.
- The deprecated protected method GdbLaunchDelegate.newServiceFactory(String) was removed. It was replaced with GdbLaunchDelegate.newServiceFactory(ILaunchConfiguration, String)
- The constructor MIThreadGroupExitedEvent(IProcessDMContext, int, String) was removed. MIThreadGroupExitedEvent(IProcessDMContext, int, MIResult[]) should be used instead.
- The constructor MITargetAttach(ICommandControlDMContext, String) was removed. MITargetAttach(IMIContainerDMContext, String) or MITargetAttach(IMIContainerDMContext, String, boolean) should be used instead.
- Based on the previous change, the method CommandFactory.createMITargetAttach(ICommandControlDMContext, String) was removed. CommandFactory.createMITargetAttach(IMIContainerDMContext, String) or CommandFactory.createMITargetAttach(IMIContainerDMContext, String, boolean) should be used instead.
- The constructors MIFileExecAndSymbols(ICommandControlDMContext) and MIFileExecAndSymbols(ICommandControlDMContext, String) where removed. MIFileExecAndSymbols(IMIContainerDMContext) and MIFileExecAndSymbols(IMIContainerDMContext, String) should be used instead.
- In GDBControl_7_0, the classes InitializationShutdownStep, CommandMonitoringStep, CommandProcessorsStep, RegisterStep were removed; their counterparts, defined in GDBControl, should be used instead.
- Based on the previous change, the class GDBControl_7_0.ListFeaturesStep now extends GDBControl.InitializationShutdownStep instead of the removed GDBControl_7_0.InitializationShutdownStep.
- MIVariableManager.MIVariableObject.setExpressionData(String,String,int) was removed. The method MIVariableManager.MIVariableObject.setExpressionData(ExpressionInfo,String,int,boolean) should be used instead.
- GdbLaunchDelegate.newServiceFactory(String) was removed. It has been replaced with GdbLaunchDelegate.newServiceFactory(ILaunchConfiguration, String)
- The methods MIDataListRegisterValues.MIDataListRegisterValues(IMIExecutionDMContext, int) and MIDataListRegisterValues.MIDataListRegisterValues(IMIExecutionDMContext, int, int[]) were removed. Callers should instead use the methods of the same name but passing in an IFrameDMContext instead of an IMIExecutionDMContext.
- Following the above change, the methods CommandFactory.MIDataListRegisterValues(IMIExecutionDMContext, int) and CommandFactory.MIDataListRegisterValues(IMIExecutionDMContext, int, int[]) have also been removed, and their corresponding methods using IFrameDMContext should be used instead.
- The method GDBRunControl_7_0_NS.eventDispatched(ITraceRecordSelectedChangedDMEvent) was removed. GDBRunControl_7_2_NS.eventDispatched(ITraceRecordSelectedChangedDMEvent) should be used instead.
- Support for the obsolete Apple GDB was removed
- The following macos packages were removed:
- org.eclipse.cdt.dsf.gdb.service.macos,
- org.eclipse.cdt.dsf.mi.service.command.commands.macos,
- org.eclipse.cdt.dsf.mi.service.command.output.macos
- org.eclipse.cdt.debug.gdbjtag.core.dsf.gdb.service.macos
- The following classes, contained in the above packages are now removed:
- MacOSCommandFactory.java
- MacOSGDBProcesses.java
- MacOSGDBRunControl.java
- MacOSGdbDebugServicesFactory.java
- MacOSMIEnvironmentCD.java
- MacOSMIVarUpdate.java
- MacOSMIVarUpdateInfo.java
- MacOSGdbJtagDebugServicesFactory.java
- The constant LaunchUtils.MACOS_GDB_MARKER was removed.
- The following macos packages were removed:
org.eclipse.cdt.managedbuilder.ui
- The class ToolChainSelectionPage was removed. It was being used by a wizard that was never used and that was removed.
org.eclipse.cdt.ui
- The classes NewCDTProjectWizard, ProjectTypePage, TemplateSelectionPage were removed. The wizard and its pages were never used and were not fully functional.
- The extension point projectTypePages was removed. It was being used by a wizard that was never used and that was removed.