CDT 8.1 - New and Noteworthy
-See What's new in CDT 8.1 on the CDT Wiki +
CDT 8.2 - New and Noteworthy
+See What's new in CDT 8.2 on the CDT Wiki which may contain more recent information.
- -Editor
+Organize Includes Command
+The Organize Includes command is similar to Organize Imports in Java. It adds missing include statements, removes unnecessary ones, and reorders includes according to user preferences. +
+
When determining which header files must be included the Organize Includes command follows the "Include What You Use" rule. See Why Include What You Use? and What Is a Use?.
-Filtering in Outline Views
-There are a few additional filtering options added to Project Explorer and Outline View: -
-
-
Mouse Hover for 'auto' Keyword
-Mouse hover for auto keyword shows deduced type: -
-
-
Refactoring
-- Code added or changed during refactoring is formatted according to user preferences. -
- New code style preferences for refactoring:
-
-
-
Indexing
-- Support for multiple variants of the same header file in the index (Bug 197989). -
- The C/C++ > Indexer > Index unused headers global preference is turned on by default (Bug 377992). -
- New command: Index > Re-resolve Unresolved Includes.
+
Build
+Console
+- Line wrap option on the console (Bug 199605).
+
-
Code Analysis
-External-tool-based Checkers
-The main motivation for integrating Codan with external tools is to enjoy all the code checks from mature tools without leaving Eclipse. With the new infrastructure: -
-- External tools can be configured using Codan’s preference page -
- External tools are invoked automatically when a C/C++ file is saved -
- The output of these tools can be displayed as editor markers -
The new infrastructure includes a sample checker that invokes Cppcheck. -
-A more detailed configuration dialog can be found by pressing the 'Customize Selected' button: -
-Users can specify the path of the Cppcheck executable and the arguments to pass to Cppcheck. -
A demo of this checker can be found here. -
The new infrastructure makes it very easy to write your own external-tool-based checker. In the simplest case, you will need to: -
-- Extend the abstract class AbstractExternalToolBasedChecker. -
- Provide the name of your tool (e.g. "Cppcheck".) -
- Provide default values for the path of the executable and arguments to pass to the executable. -
- Register a IErrorParser in the extension point "org.eclipse.cdt.core.ErrorParser" with context "codan". This parser parses the output of the external tool, line by line. It’s up to you to decide what to do with the output (e.g. create error markers.)
+
Improved toolchain detection
+- Automatic detection of MinGW 64 bit (Bug 380598). +
- Detection of Visual Studio under Windows 7 64 bit (Bug 385608). +
- Recognize $PATH environment variable from workspace preferences for MinGW and Cygwin toolchains (Bug 384520). +
- Introduction of environment variables $MINGW_HOME and $CYGWIN_HOME that are recognized in preferences and project properties (Bug 403257, Bug 357442).
Please take a look at the source code of CppcheckChecker for details. -
In the case of tools that are complex to set up, the new infrastructure is extremely flexible and configurable. It allows you to pretty much to configure every single aspect of the checker, from the files that the tool can check to the way to feed arguments to the tool. +
-
New Codan checkers
-- Class members should be properly initialized (Bug 339795). Example:
+
Scanner Discovery / Language Settings Providers
+- "Preprocessor Include Paths, Macros etc." property page now fully replaces older "Scanner Discovery" page. "Scanner Discovery" is now hidden by default (Bug 403405, Bug 407087).
struct Demo { - Demo() {} // Warning: Member 'field' was not initialized in this constructor - - int field; - }; +
+
+- Built-in Compiler Settings provider for MinGW is enabled by default now for MinGW toolchain (Bug 382422). +
- Added Built-in Compiler Settings provider for Cygwin (Bug 382423). +
+
+- Project-relative include paths representation was stabilized and now officially supported in UI (Bug 401734). +
- Support for project-relative paths for Build Output Providers (Bug 402023). +
- Changes in environment variables (preferences or project properties - as applicable) automatically trigger re-discovery (Bug 403406). +
- Number of changes to support compatibility with older methods to provide include paths for indexer, namely pathEntryContainers, contributed ScannerInfo entries (Bug 401961, Bug 398056, Bug 392966). +
- Fixed compatibility issues related to import older projects (Bug 393641). +
Makefile Editor
+- GNU Makefile functions highlighting fixed (Bug 406911). +
- Bracket matching (Bug 405279). +
+
+- Content assist for automatic variables (Bug 407169). +
+
+- Highlight for conditional variable assignment (Bug 406596). +
- Proper colorization of escaped # (Bug 404599). +
Misc
+- Ability to specify local includes for indexer, as in [#include "header.h"] as opposed to system includes [#include <header.h>] (Bug 388368). +
- Fixed some bugs related to storing environment variables, such as silently ignoring removals or additions (Bug 348781, Bug 355488). +
- Improved performance in certain areas (Bug 405643, Bug 405638, Bug 405744, Bug 407483). +
Debug
+Enhanced Expressions
+The Expressions view has been extended to allow the user to manually create enhanced-expressions. Enhanced-expressions define a set of expressions which can be easily described using glob-pattern matching. The user specifies an enhanced-expression by prefixing it with '='. For example: +
+- pattern-matched sorted groups of local variables, where the symbols * [] ? can be used e.g., +
=v?r -- Will show local variables starting with a 'v' and ending with 'r' with a single character in between +=* -- Will show all local variables of the selected stack frame in sorted order (the '=' is optional for this expression, i.e., '*') +=*x -- Will show local variables ending with 'x'
-
+- array ranges including glob-expressions +
=array[30-40] -- Will show array elements from 30 to 40 +=array[1-5,20,30-31] -- Will show array elements from 1 to 5, 20 and 30 to 31 +=array?[1-5] -- Will show array elements from 1 to 5 for any array starting with 'array' followed by a single character +
+- pattern-matched sorted registers groups, where the symbols * [] ? can be used e.g., +
=$e?x -- Will show all registers starting with 'e' and ending with 'x' with a single character in between +=$* -- Will show all registers (the '=' is optional for this expression, i.e., '$*') +=$*x -- Will show registers ending with 'x' +=$st[3-5] -- Will show registers $st3, $st4, $st5 +
+- semi-colon-separated, individually sorted groups of expressions, e.g, +
var1; var2 -- Will create a group containing both var1 and var2 +$eax; var1 -- Will show a group containing register $eax and variable var1 +var1; =$e* -- Will show a group containing variable var1 as well as all registers starting with 'e' +
+This feature allows to quickly define multiple expressions that interest the user. Because groups are created from these special expressions, they can be collapsed when uninteresting and re-expanded later, without having to be re-entered by the user. +
+This feature was completed on July 10th, 2012 and updated for local variables on December 19th, 2012. For details see Bug 381754 and Bug 394408. +
Note that the comma (,) is not allowed as a group separator as it is used within valid expressions that use templates (e.g., ((((((class std::_Vector_base<int, std::allocator<int> >) v))._M_impl))._M_start)).
-Build
-Scanner Discovery
-Scanner Discovery has been reworked in this release. The main purpose of Scanner Discovery was always to supply Include Paths and Macros for indexer and build. Now these are supplied by Language Settings Providers. See more at Scanner Discovery on the wiki. -
-OS Resources View
+CDT has a new view called "OS Resources". This view will display different information about the resources of the operating system. For example, it can give a list of all processes running on the target. The view will display the information as provided by GDB. +
+As of writing, GDB supported the following information: +
+Processes - Listing of all processes +Process groups - Listing of all process groups +Threads - Listing of all threads +File descriptors - Listing of all file descriptors +Sockets - Listing of all internet-domain sockets +Shared-memory regions - Listing of all shared-memory regions +Semaphores - Listing of all semaphores +Message queues - Listing of all message queues +Kernel modules - Listing of all loaded kernel modules +
+
+
Notes: +- For performance reasons, the view is not automatically refreshed. Press the Refresh button on the the view toolbar to fetch the latest information. Hovering over this Refresh button will display the time at which the information was last obtained. +
- Columns can be re-sized. +
- Columns can be removed or added using the view menu. +
- Entries can be ordered by column by pressing on the column header. +
- When doing debugging of a remote target, the information in the view pertains to the remote target. +
This feature requires GDB 7.5 and higher. Furthermore, as of GDB 7.5, this feature only works for Linux. +
This feature was completed on September 20th, 2012. For details see Bug 360314. +
+Breakpoint Filtering
+The CDT has enhanced the standard behavior of the "Show Breakpoints Supported by Selected Target" option of the Breakpoints view. Using this option with the CDT will now only show breakpoints that are actually applicable to the current debug session. Therefore, when debugging a C/C++ application, the user will not be bothered with the breakpoints set in the code of an another C/C++ application. +
+For backwards-compatibility, a preference is provided to revert this new behavior to the original one. The original behavior of this option is to have the Breakpoints view show all breakpoints that are of the same type as the current debug session. For example, if debugging Java, only Java breakpoints would be shown, and if debugging C/C++ only C/C++ breakpoints would be shown. This preference can be found under "C/C++ -> Debug -> GDB -> Use aggressive breakpoint filtering". +
This feature was completed on October 26th, 2012. For details see Bug 360735. +
+Enhanced GDB console support
+CDT is being improved to update its views with any change made to GDB by the user from the GDB console. Updates are being added gradually and the final goal is to allow the user to perform any command from the GDB console, and have CDT stay synchronized with the changes. +
+Breakpoints, watchpoints and tracepoints
+Breakpoints, watchpoints or tracepoints set from the GDB console are now shown in the Breakpoints view. All breakpoint related GDB commands are supported and synchronized with the UI. No support for catchpoints yet. This feature requires GDB 7.4 or higher. +
This feature was completed on November 29th, 2012. For details see Bug 392512. +
+Memory and variables
+Memory and variables modified from the GDB console are now updated in the Memory, Memory Browser, Variables and Expressions views. This feature requires GDB 7.6 or higher. +
This feature was completed on January 26th, 2013. For details see Bug 397715. +
+Reverse debugging state
+CDT will now properly update the status of reverse debugging if its state is modified through the GDB console. This feature requires GDB 7.6 or higher. +
This feature was completed on January 31st, 2013. For details see Bug 399163 +
+Breakpoint actions to control reverse debugging
+It's now possible to control the enabling, disabling and toggling of the reverse debugging mode, through breakpoint actions. The reverse debugging mode can be useful to debug, but has a significant performance cost when enabled. Using the new breakpoint action to enable the reverse debug mode, one can program a breakpoint to enable that mode in the vicinity of the suspected source code. That way, until that point is reached, no performance impacts are felt. +
To use this feature, right-click on a breakpoint and select "Breakpoint Properties". Then in the left page, chose "Actions". Then click "New". In the new dialog, select the Action Type "Reverse Debug Action". Then chose if the action should enable, disable or toggle the reverse debug mode. Finally chose a name for the action. When done, click "Ok" +
+The newly created action will appear in the list of available actions, that can be attached to any breakpoint To attach it to the current breakpoint, click on "Attach". +
+Note: For the reverse debug breakpoint actions to work, reverse debugging must be available in the current debug session. For instance, it will not work if the "non-stop" mode is active. +
This feature was completed on December 13th, 2012. For details see Bug 365776. +
+Floating Point renderer has been added to the memory package
+A floating point render has been added to the memory package. So now there is the Traditional renderer and a Floating Point renderer available. This render allows display and editing of the floating point values. Since it originated from the Traditional render, it's workflow and style are similar. There is no ASCII data pane display, since this did not seem to make much sense with floating point data. +
+This feature was completed on November 16th, 2012 as part of Bug 394509. +
+Debugging multiple processes within one debug session
+Debugging a new executable in the same debug session has been improved for GDB versions starting from 7.2. "Debug New Executable" action has been added to the context menu of the Debug view. +
+
+The dialog for specifying an executable to debug for local sessions has been changed. +
+
+The ability to debug a remote executable using gdbserver has been added. +
+This feature was completed on January 25th, 2013. For details see Bug 344890.
-
Mac OSX Frameworks
-The new scanner discovery makes it possible to discover and use with indexer Mac OSX Frameworks folders, see bug 69529 -
Load information in the Multicore Visualizer - CPU/core load meters
+The Multicore Visualizer view has been enhanced to support system load monitoring, in the form of graphical load meters, showing the load of the system being debugged (local or remote). This works only on Linux targets for now. By default this feature is disabled, as it may cause a bit of increased load when remote-debugging. Here is what it looks-like, when enabled: +
+When enabled and space permits, a load meter is displayed for each core and also one for each CPU, that shows the average load for all contained cores. +
To enable the load meters, one has to use the context menu of the Multicore Visualizer; right-click on the visualizer, go into the "Load Meters" sub-menu and select "Enable Load Meters" : +
+It's also possible to choose the load meters refresh interval. When the load meters are enabled, a "Refresh Speed" entry is added to the Load Meters sub-menu. There you have a choice of three refresh speeds. Selecting one makes it take effect. +
-
+This feature was completed on February 28th, 2013. For details see Bug 396268.Console
-Build console marks more prominently start and end of build and reports elapsed time: -
-Edit Tracepoint on Create
+It is no longer necessary to first create a CDT Tracepoint, then edit its properties. Properties such as enabled, pass count, condition, can be set while creating the tracepoint. +
There are different methods to open the properties dialog before creating the Tracepoint. First, using the editor popup menu by right-clicking on the editor gutter, one must set the Breakpoint Type to "C/C++ Tracepoints".
-Parallel Build
-Parallel Build was remodelled, see bug 259768: -
-
-
-Managed Build
-A few additional options to select from added to managed build, bug 365461. -
-
-
-Debug
-Multicore Visualizer View
-CDT now optionally includes a Multicore Visualizer View. This view displays a graphical representation of the state of the current application. It allows one to click- and drag-select groups of processes/threads, and apply debugging commands to them directly from the visualizer. Selections made in the Visualizer View are reflected automatically in the Debug View, and vice versa. The Multicore Visualizer View is designed to scale to large numbers of cpus and cores-per-cpu on both current and future multicore hardware. -
The Multicore Visualizer View is meant to serve as a high-level visual overview of the current application, and can be used in tandem with the Debug View, which provides more in-depth detail. -
The Multicore Visualizer View is just one example of a visualizer based on the underlying Visualizer Framework plugin. This provides a pluggable, extensible platform for developing visual development tools of this kind. -
-Note that the Multicore Visualizer will only work using a Linux target; it will not work debugging on a Windows or Mac target. This is a current limitation of GDB which does not provide information about cores, for those targets (at writing, GDB is at version 7.4). -
This feature was completed on February 10th, 2012. For details see Bug 335027 -
The Multicore Visualizer is an optional feature of the CDT and must be installed manually. The feature is called
-C/C++ Multicore Visualizer
. Installing it will install both the Multicore Visualizer and the Visualizer Framework. If you only want to install the Visualizer Framework (to build your own visualizer), you can install that feature by itself; it is calledCDT Visualizer Framework
. Once the features are installed, you can access the Multicore Visualizer (or any other visualizer) by opening the view calledVisualizer
. -Partitioning of large arrays
-CDT now displays large arrays as collections of partitions. -
-This feature was completed on January 26th, 2012 as part of Bug 365541 -
-Edit Breakpoint on Create
-It is no longer necessary to first create a CDT breakpoint, then edit its properties. Properties such as enabled, ignore count, condition, temporary, can be set while creating the breakpoint. -
There are several methods to open the properties dialog before creating the breakpoint: -
-- Add Breakpoint action.
-
- In the editor or the disassembly view, bring up the popup menu on the gutter. -
- Select the Add Breakpoint... menu item. -
- This brings up the breakpoint properties dialog for a line breakpoint pre-filled with the breakpoints location.
+
- Add Breakpoint action.
+
- Select the Add Breakpoint... menu item. +
- This brings up the tracepoint properties dialog for a line tracepoint pre-filled with the tracepoint's location.
- Control-Double Click
- Hold the Control key while double-clicking on the editor gutter. -
- This brings up the breakpoint properties dialog for a line breakpoint pre-filled with the breakpoints location. -
- Control key with Toggle Method Breakpoint
-
- Open the editor's Outline view. -
- Right-click on a method to bring up the popup menu. -
- Hold the control key while selecting the Toggle Method Breakpoint action. -
- This brings up the function breakpoint dialog pre-filled with the method name. -
- Add Watchpoint (C/C++)
-
- In the Breakpoints view, open the view menu. -
- Select the Add Watchpoint (C/C++)... action. -
- This brings up the watchpoint properties dialog. -
- User must enter the watchpoint expression. -
- Add Function Breakpoint (C/C++)
-
- In the Breakpoints view, open the view menu. -
- Select the Add Function Breakpoint (C/C++)... action. -
- This brings up the function breakpoint properties dialog. -
- User must enter the function expression. +
- This brings up the breakpoint properties dialog for a line breakpoint pre-filled with the breakpoints location.
-
-Image: The breakpoint properties dialog for a line breakpoint about to be created. +
Step Into Selection
+With the DSF debugger it is now possible to select a function to step into.
-
+The selected method can be in a different line than the one under execution
+The two main methods to do this areBreakpoint Toggle Short-Cuts
-The Toggle Breakpoint action in the editor and disassembly view menu now supports new behaviors when used with modifier keys: -
-- Hold the Shift key while double-clicking on an existing breakpoint in order to enable or disable the breakpoint. -
- Hold the Control key while double-clicking on an existing breakpoint in order to bring up the breakpoint properties dialog to edit the existing breakpoint. -
- Hold the Control key while double-clicking on a location with no breakpoints, in order to bring up the breakpoint properties dialog to create a new breakpoint.
+
- Using the context menu
-Image:The editor gutter popup menu with the hints for the new accelerators. +
Select a method, right-click and select "Step Into Selection"
+or use the short key Ctrl+F5 +
-
Function Breakpoint Manual Entry
-There is a new option for creating a function breakpoint: -
-- Open the Breakpoints view menu. -
- Select Add Function Breakpoint C/C++. -
- Fill in the function name or expression and select OK to create breakpoint. -
Advanced character encoding support
-CDT now supports the handling of different character encodings for strings and wide character strings while debugging. This includes full support for Unicode encodings and many other popular encodings as well. You can select the character and wide character encoding within the Debug preferences. -
-CDT will then correctly display strings according to the selected encoding while debugging. -
-Note that this feature requires GDB version 7.0 or later. This feature was completed on March 7th, 2012 as part of Bug 307311, Bug 367456 and Bug 370462. -
-Timeout support for GDB commands in DSF/GDB
-Timeouts for GDB commands are now supported in DSF/GDB. The feature is optional and disabled by default. The timeout values are configurable. When the feature is enabled, custom values can be assigned to some commands, all other commands use the default value. This feature was completed on April 17th, 2012 as part of Bug 361934. -
-
-
-
-Multi-select Resume/Suspend operations
-CDT now allows to perform a Resume or Suspend operation on multiple selections of the same debug session. Because such a concept only adds value in a Non-Stop debug session, it is only supported in such a session (see Non-Stop Debugging). The behavior of a multi-selection Resume/Suspend is as follows: -
-- Any selected stack frames implies a selection of their corresponding thread. -
- If one or more threads are selected (not processes) and the resume/suspend operation is triggered, each selected thread on which the operation is currently valid will be resumed/suspended. -
- If one or more processes are selected (not threads) and the resume/suspend operation is triggered, each selected process will be resumed/suspended. Resuming/suspending a process implies resuming/suspending each one of its threads on which the operation is currently valid. -
- If both thread(s) and process(es) are selected, and the resume/suspend operation is triggered, each selected process will be resumed/suspended, and each selected thread which is not part of any selected process will be resumed/suspended. The idea is that if a process is being resumed/suspended, each of its threads will be automatically resumed/suspended, and therefore, should not be resumed/suspended a second time because it is also selected.
+
- Using the hyper link navigation
As hinted above, CDT takes a permissive approach to multi-select resume/suspend. This means that if a multi-selection includes both stopped and running threads, a resume operation is still allowed, and only the suspended threads will be resumed; similarly, on such a multi-selection, a suspend operation is allowed, and only the running threads will be suspended. +
Press Ctrl-Alt, hover over a function and mouse click on it +
+NOTE: This first implementation runs to the selected line, steps into its methods and stops when a method is entered having the same name and number of arguments of the selected method i.e. Argument types are not validated at this point. +
This feature was completed on May 1st, 2013. For details see Bug 244865.
-Example
-
-In the above screenshot if the user were to press the Resume button with the current multi-selection the following would happen: -
-- The Consumer process node is selected, therefore the entire process will be resumed. This means that the suspended threads 7 and 9 will be resumed, while threads 6, 8 and 10 will be ignored, as they are already running. -
- Note that the fact that threads 9 and 10 are selected is ignored, as those threads are part of the selected Consumer process, which will be resumed. -
- Stack frames doWork() and work() are selected and belong to thread 4, which becomes implicitly selected in their place. Thread 4 will therefore be resumed. -
- Thread 2 is selected and suspended, and will be resumed. -
- Thread 5 is selected but running, so it will be ignored. -
This feature was completed April 25th, 2012 as part of Bug 330974 -
-Show only suspended threads in Debug view
-CDT now has an global preference that allows to only show the suspended threads within the Debug view. When dealing with a large number of threads, a user is typically interested by the threads that are being inspected (suspended ones) and does not care about the running ones. Using this preference, all running threads will not be shown in the Debug view. Note that when a thread is stepping it will remain visible, although it is technically running. The process element of the Debug view will show how many threads are currently being filtered from view. -
The below example shows the exact same debugging session. The first screenshot only shows suspended threads, while the second shows all threads. -
-
-Below shows how to access the preference, which is disabled by default. -
-This feature was completed May 4th, 2012 as part of Bug 375585 -
-Multi-select attach dialog
-CDT now allows selecting more than one process to attach to in a single user operation. The bottom pane is used to see which processes have been selected. If multi-process debugging is not supported with your debug session (needs GDB >= 7.2 and NonStop enabled), only the first process will be attached to. -
-This feature was completed June 30th, 2011 as part of Bug 293679 -
-Default Postmortem file location
-CDT now allows the user to specify a default directory for the location of core files for a postmortem launch when the prompt is triggered. Since a postmortem launch can easily be re-used for different core files of the same binary, this feature helps reduce the amount of navigation needed to select a core file. Note that specifying the actual core file is still supported, as well as leaving the entire field blank, which will also trigger the prompt, but use the default directory for its starting location. -
Note that this 'core file' field supports the use of variables such as ${workspace_loc}. -
This feature applies to both core files and trace files. -
-This feature was completed on February 17th, 2012 as part of Bug 362039 -
-Support for Fast Tracepoints
-CDT now allows the user of fast tracepoints, as supported by GDB. Fast tracepoints use an instruction jump instead of a trap for efficiency. Fast tracepoint need a minimum of space to be inserted in the program and therefore, may fail to be set at certain locations. For fast tracepoints to work, a special library called the in-process agent (IPA), must be loaded in the inferior process. This library is built and distributed as an integral part of gdbserver. Please see the GDB documentation for more details. -
The user can select between three tracepoint modes in the launch: -
-- Fast: Only use fast tracepoints. No tracepoint will be planted if a fast tracepoint cannot be used. -
- Normal: Only use normal tracepoints. -
- Automatic: Attempt to use fast tracepoints. If a fast tracepoint cannot be used, automatically use a normal tracepoint. -
-This feature was completed July 20th, 2011 as part of Bug 346320 -
-Enhancements to Tracepoints
-With the use of GDB 7.4, some new features are available within Eclipse. -
-- Live enable/disable of C/C++ Tracepoints
-
- Tracepoints can now be enabled and disabled at any time after a trace experiment has been started, and will immediately take effect within the ongoing experiment. -
- Note: Although GDB 7.4 seems to allow a tracepoint to be created during a trace experiment and will add it to the ongoing experiment, this behavior seems to have some issues. One of which is that deleting a tracepoint during an experiment will not remove that tracepoint from the ongoing experiment. Until this is fixed in GDB, it is recommended that the user stick to enable/disable operations during a tracing experiment.
-
- Smaller Fast tracepoints
-
- On 32-bit x86-architectures, fast tracepoints can now be placed at locations with 4-byte instructions, when they were previously limited to locations with instructions of 5 bytes or longer. -
- Tracepoint collecting of Strings
-
- The tracepoint Collect action now has an option to request to collect character pointers as strings. It tells GDB to effectively dereference pointer-to-character types and collect the bytes of memory up to a zero byte. An optional integer limit sets a bound on the number of bytes that will be collected. This feature was completed on April 20th, 2012. For details see Bug 373707 -
-
-
-Show the actual variable type based on RTTI
-With GDB 7.5 or higher CDT could show the actual variable type (not the declared one) in Variables and Expressions Views. Consider the following example: -
-struct SuperInterface { - virtual ~SuperInterface() {} // enable RTTI for Interface class - }; - - struct TheImplementation : public SuperInterface { - TheImplementation(int _v1, float _v2) - : someField(_v1), anotherField(_v2) {} - - int someField; - float anotherField; - }; - - - int main() { - SuperInterface* i = new TheImplementation(42, 4.2); - return 0; // [Launch debug until here] - } --Launch the debugging session and run until return statement: -
-This feature is enabled by default and will work if you have the proper GDB version (7.5 or higher) and RTTI generation enabled (enabled by default in gcc), however it could be turned off in preferences: -
-This feature was completed on May 5th, 2012 as part of Bug 376901 and Bug 377536. -
-Build variables support in "C/C++ Application" field of launch configuration
-
-There are also a few new CDT-specific build variables: -
-- config_name - the name of the active configuration for the project specified as an argument; -
- config_description - the description of the active configuration for the project specified as an argument; -
This feature was completed on April 2nd, 2012 as part of Bug 180256 and Bug 375814. -
-Support for octal number format in CDI
-CDI now also supports to use the octal number format to display the contents of variables, expressions and registers. You can select the octal number format within the Debug preferences. This feature was completed on March 7th, 2012 as part of Bug 370462. +
Multicore Visualizer enhanced selection and filtering
+The multicore visualizer has been enhanced so that it's now possible to select CPUs and cores, in addition to threads. The previous selection methods still work (ctrl-left-click add-to-selection, left-click and drag, etc), but now are also applicable to CPU and core graphical objects. +
+This feature was completed on April 26th, 2013. For details see Bug 404894.
+Building on the enhanced selection, it's now also possible to filter what is shown in the multicore visualizer. This is especially useful in cases where there are many CPUs/cores/threads, and one wants to concentrate on a subset. To filter the view, first select the graphical elements you want to keep, then from the context menu, chose "Filter to selection". The selected graphical elements will be shown, along with any parent objects; for instance a thread will be shown in its core and CPU. The filter stays in place until cleared, using the context menu "Clear filter". +
+This feature was completed on May 6th, 2013. For details see Bug 405390.
-C/C++ Unit Testing Support
-
-
-Process exit code shown in console
+When a process completes execution normally, its exit code is shown in the title of that process' console. If the process is terminated or disconnected by the user, no exit code will be shown. +
+Note that if there is no process console, then no exit code can be displayed. This affects remote debugging and attach debugging. We hope to address this in the next release of CDT. +
This feature was completed on May 6th, 2013. For details see Bug 402054.
-- tests running with support of the following frameworks:
-
- Boost.Test; -
- Qt Test; -
- Google Testing Framework;
+
Important Notes
+Although CDT 8.2 is meant to be a backwards-compatible release, the following exceptions should be noted. +
+- The package org.eclipse.cdt.dsf.gdb.multicorevisualizer.internal was made API by mistake when first released. It has now been officially marked internal. Note that the package has always had the word 'internal' in its name. We don't believe there are any extenders to this package yet.
- tests hierarchy browsing; -
- test messages viewing, filtering by test or test suite; source lookup is also supported; -
- testing statistics (total/failed/aborted tests count, red/green bar); -
- testing time measurement; -
- tests hierarchy filters (show only failed tests); -
- running & rerunning only selected tests (not a whole test module); -
- start a debug session for the whole test module or only the selected tests; -
- test messages filters (by severity); -
- test runs history; -
- the list of provided tests runners may be easily extended writing a new Tests Runner Plugin. -
The HOWTO, known problems and limitation can be found in the CDT FAQ on the wiki. -
This feature was completed April 18th, 2012 as part of Bug 210366. -
-Bugs Fixed in this Release
-Bugzilla tasks completed for this release: - -CDT 8.1 bug fixes -
+
-What's new in other CDT releases
To learn what's new in other CDT releases see:
+ diff --git a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_60.htm b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_60.htm index e90d4300006..09577af1449 100644 --- a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_60.htm +++ b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_60.htm @@ -455,6 +455,7 @@ See What's New in CDT 5.0To learn what's new in CDT releases see:
+ diff --git a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_70.htm b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_70.htm index 0a6852755ee..144c0d7f85e 100644 --- a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_70.htm +++ b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_70.htm @@ -336,6 +336,7 @@ which may contain more recent information.To learn what's new in CDT releases see:
+ diff --git a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_80.htm b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_80.htm index 2aaf44afac1..85fb7b880c7 100644 --- a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_80.htm +++ b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_80.htm @@ -543,6 +543,8 @@ endTo learn what's new in CDT releases see:
+ + diff --git a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_81.htm b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_81.htm new file mode 100644 index 00000000000..48d47c18ebe --- /dev/null +++ b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew_81.htm @@ -0,0 +1,400 @@ + + + + + + + +CDT 8.1 New and Noteworthy + + + +++ + diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/BpFilter.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/BpFilter.png new file mode 100644 index 00000000000..e4b57a84e85 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/BpFilter.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-Filtering.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-Filtering.png new file mode 100644 index 00000000000..d4e2325de8e Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-Filtering.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-LoadMeters-enabling2.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-LoadMeters-enabling2.png new file mode 100644 index 00000000000..b6132ca6e7b Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-LoadMeters-enabling2.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-LoadMeters.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-LoadMeters.png new file mode 100644 index 00000000000..a5f7077a033 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-LoadMeters.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-Selection.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-Selection.png new file mode 100644 index 00000000000..f3e8c1039fc Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-Selection.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-selecting_loadMeters_refresh_speed.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-selecting_loadMeters_refresh_speed.png new file mode 100644 index 00000000000..6446a447048 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-MulticoreVisualizer-selecting_loadMeters_refresh_speed.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-RevBPAction-create.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-RevBPAction-create.png new file mode 100644 index 00000000000..3a082ae8678 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-RevBPAction-create.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-RevBPAction-dialog.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-RevBPAction-dialog.png new file mode 100644 index 00000000000..ff9feb3015c Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT-DSF-GDB-RevBPAction-dialog.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_DebugNewExecutableMenu.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_DebugNewExecutableMenu.png new file mode 100644 index 00000000000..5fb4d1b639c Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_DebugNewExecutableMenu.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_Debug_ExitCode.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_Debug_ExitCode.png new file mode 100644 index 00000000000..0e622a09f4d Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_Debug_ExitCode.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_FloatingPointMemory.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_FloatingPointMemory.png new file mode 100644 index 00000000000..71405e4de64 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_FloatingPointMemory.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_GroupExpr.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_GroupExpr.png new file mode 100644 index 00000000000..8f51113a9dd Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_GroupExpr.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_NewExecutableDialog_Local.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_NewExecutableDialog_Local.png new file mode 100644 index 00000000000..3ced0a8297a Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_NewExecutableDialog_Local.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_NewExecutableDialog_Remote.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_NewExecutableDialog_Remote.png new file mode 100644 index 00000000000..595cbaec554 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_NewExecutableDialog_Remote.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_OSResources.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_OSResources.png new file mode 100644 index 00000000000..716aeb4726d Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CDT_OSResources.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CYGWIN_HOME.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CYGWIN_HOME.png new file mode 100644 index 00000000000..06c07def2a4 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CYGWIN_HOME.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/ConsoleWrapLine.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/ConsoleWrapLine.png new file mode 100644 index 00000000000..aa53865050f Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/ConsoleWrapLine.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/ConsoleWrapLinePreference.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/ConsoleWrapLinePreference.png new file mode 100644 index 00000000000..433c1e74f51 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/ConsoleWrapLinePreference.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/CygwinProvider.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/CygwinProvider.png new file mode 100644 index 00000000000..752a51a6788 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/CygwinProvider.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/MINGW_HOME.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/MINGW_HOME.png new file mode 100644 index 00000000000..c5ac5128108 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/MINGW_HOME.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/MakeEditorBracketMatching.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/MakeEditorBracketMatching.png new file mode 100644 index 00000000000..c2c162dde38 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/MakeEditorBracketMatching.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/MakeEditorContentAssistAutoVars.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/MakeEditorContentAssistAutoVars.png new file mode 100644 index 00000000000..0b246c331ec Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/MakeEditorContentAssistAutoVars.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/OrganizeIncludes.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/OrganizeIncludes.png new file mode 100644 index 00000000000..6de2b1065ca Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/OrganizeIncludes.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/PropertyPageSettingsScannerDiscovery.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/PropertyPageSettingsScannerDiscovery.png new file mode 100644 index 00000000000..6b0c13dc673 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/PropertyPageSettingsScannerDiscovery.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/StepIntoSelction.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/StepIntoSelction.png new file mode 100644 index 00000000000..22a42da349c Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/StepIntoSelction.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/cdt82/StepIntoSelectionHyperLink.png b/doc/org.eclipse.cdt.doc.user/images/cdt82/StepIntoSelectionHyperLink.png new file mode 100644 index 00000000000..9990f1a3d1d Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/cdt82/StepIntoSelectionHyperLink.png differCDT 8.1 - New and Noteworthy
+See What's new in CDT 8.1 on the CDT Wiki + which may contain more recent information. +
+ +
+ ++Contents
-
+
- 1 Editor + + +
- 2 Refactoring +
- 3 Indexing +
- 4 Code Analysis + + +
- 5 Build + + +
- 6 Debug
+
-
+
- 6.1 Multicore Visualizer View +
- 6.2 Partitioning of large arrays +
- 6.3 Edit Breakpoint on Create +
- 6.4 Breakpoint Toggle Short-Cuts +
- 6.5 Function Breakpoint Manual Entry +
- 6.6 Advanced character encoding support +
- 6.7 Timeout support for GDB commands in DSF/GDB +
- 6.8 Multi-select Resume/Suspend operations +
- 6.9 Show only suspended threads in Debug view +
- 6.10 Multi-select attach dialog +
- 6.11 Default Postmortem file location +
- 6.12 Support for Fast Tracepoints +
- 6.13 Enhancements to Tracepoints +
- 6.14 Show the actual variable type based on RTTI +
- 6.15 Build variables support in "C/C++ Application" field of launch configuration +
- 6.16 Support for octal number format in CDI +
+ - 7 C/C++ Unit Testing Support +
- 8 Bugs Fixed in this Release +
Editor
+Pin the Call Hierarchy View
+The Call Hierarchy View can now be pinned which enables the user to open multiple Call Hierarchy views at the same time. +
+This feature was completed November 12th, 2011 as part of Bug 342498 +
+
+Filtering in Outline Views
+There are a few additional filtering options added to Project Explorer and Outline View: +
+
+
+Mouse Hover for 'auto' Keyword
+Mouse hover for auto keyword shows deduced type: +
+
+
+Refactoring
+- Code added or changed during refactoring is formatted according to user preferences. +
- New code style preferences for refactoring:
+
+
+
+Indexing
+- Support for multiple variants of the same header file in the index (Bug 197989). +
- The C/C++ > Indexer > Index unused headers global preference is turned on by default (Bug 377992). +
- New command: Index > Re-resolve Unresolved Includes. +
+
+Code Analysis
+External-tool-based Checkers
+The main motivation for integrating Codan with external tools is to enjoy all the code checks from mature tools without leaving Eclipse. With the new infrastructure: +
+- External tools can be configured using Codan’s preference page +
- External tools are invoked automatically when a C/C++ file is saved +
- The output of these tools can be displayed as editor markers +
The new infrastructure includes a sample checker that invokes Cppcheck. +
+A more detailed configuration dialog can be found by pressing the 'Customize Selected' button: +
+Users can specify the path of the Cppcheck executable and the arguments to pass to Cppcheck. +
A demo of this checker can be found here. +
The new infrastructure makes it very easy to write your own external-tool-based checker. In the simplest case, you will need to: +
+- Extend the abstract class AbstractExternalToolBasedChecker. +
- Provide the name of your tool (e.g. "Cppcheck".) +
- Provide default values for the path of the executable and arguments to pass to the executable. +
- Register a IErrorParser in the extension point "org.eclipse.cdt.core.ErrorParser" with context "codan". This parser parses the output of the external tool, line by line. It’s up to you to decide what to do with the output (e.g. create error markers.) +
Please take a look at the source code of CppcheckChecker for details. +
In the case of tools that are complex to set up, the new infrastructure is extremely flexible and configurable. It allows you to pretty much to configure every single aspect of the checker, from the files that the tool can check to the way to feed arguments to the tool. +
+New Codan checkers
+- Class members should be properly initialized (Bug 339795). Example: +
struct Demo { + Demo() {} // Warning: Member 'field' was not initialized in this constructor + + int field; + }; ++
+
+Build
+Scanner Discovery
+Scanner Discovery has been reworked in this release. The main purpose of Scanner Discovery was always to supply Include Paths and Macros for indexer and build. Now these are supplied by Language Settings Providers. See more at Scanner Discovery on the wiki. +
+
+
+
+Mac OSX Frameworks
+The new scanner discovery makes it possible to discover and use with indexer Mac OSX Frameworks folders, see bug 69529 +
+
+
+Console
+Build console marks more prominently start and end of build and reports elapsed time: +
+
+
+Parallel Build
+Parallel Build was remodelled, see bug 259768: +
+
+
+Managed Build
+A few additional options to select from added to managed build, bug 365461. +
+
+
+Debug
+Multicore Visualizer View
+CDT now optionally includes a Multicore Visualizer View. This view displays a graphical representation of the state of the current application. It allows one to click- and drag-select groups of processes/threads, and apply debugging commands to them directly from the visualizer. Selections made in the Visualizer View are reflected automatically in the Debug View, and vice versa. The Multicore Visualizer View is designed to scale to large numbers of cpus and cores-per-cpu on both current and future multicore hardware. +
The Multicore Visualizer View is meant to serve as a high-level visual overview of the current application, and can be used in tandem with the Debug View, which provides more in-depth detail. +
The Multicore Visualizer View is just one example of a visualizer based on the underlying Visualizer Framework plugin. This provides a pluggable, extensible platform for developing visual development tools of this kind. +
+Note that the Multicore Visualizer will only work using a Linux target; it will not work debugging on a Windows or Mac target. This is a current limitation of GDB which does not provide information about cores, for those targets (at writing, GDB is at version 7.4). +
This feature was completed on February 10th, 2012. For details see Bug 335027 +
The Multicore Visualizer is an optional feature of the CDT and must be installed manually. The feature is called
+C/C++ Multicore Visualizer
. Installing it will install both the Multicore Visualizer and the Visualizer Framework. If you only want to install the Visualizer Framework (to build your own visualizer), you can install that feature by itself; it is calledCDT Visualizer Framework
. Once the features are installed, you can access the Multicore Visualizer (or any other visualizer) by opening the view calledVisualizer
. +Partitioning of large arrays
+CDT now displays large arrays as collections of partitions. +
+This feature was completed on January 26th, 2012 as part of Bug 365541 +
+Edit Breakpoint on Create
+It is no longer necessary to first create a CDT breakpoint, then edit its properties. Properties such as enabled, ignore count, condition, temporary, can be set while creating the breakpoint. +
There are several methods to open the properties dialog before creating the breakpoint: +
+- Add Breakpoint action.
+
- In the editor or the disassembly view, bring up the popup menu on the gutter. +
- Select the Add Breakpoint... menu item. +
- This brings up the breakpoint properties dialog for a line breakpoint pre-filled with the breakpoints location. +
- Control-Double Click
+
- Hold the Control key while double-clicking on the editor gutter. +
- This brings up the breakpoint properties dialog for a line breakpoint pre-filled with the breakpoints location. +
- Control key with Toggle Method Breakpoint
+
- Open the editor's Outline view. +
- Right-click on a method to bring up the popup menu. +
- Hold the control key while selecting the Toggle Method Breakpoint action. +
- This brings up the function breakpoint dialog pre-filled with the method name. +
- Add Watchpoint (C/C++)
+
- In the Breakpoints view, open the view menu. +
- Select the Add Watchpoint (C/C++)... action. +
- This brings up the watchpoint properties dialog. +
- User must enter the watchpoint expression. +
- Add Function Breakpoint (C/C++)
+
- In the Breakpoints view, open the view menu. +
- Select the Add Function Breakpoint (C/C++)... action. +
- This brings up the function breakpoint properties dialog. +
- User must enter the function expression. +
+
+Image: The breakpoint properties dialog for a line breakpoint about to be created. +
+Breakpoint Toggle Short-Cuts
+The Toggle Breakpoint action in the editor and disassembly view menu now supports new behaviors when used with modifier keys: +
+- Hold the Shift key while double-clicking on an existing breakpoint in order to enable or disable the breakpoint. +
- Hold the Control key while double-clicking on an existing breakpoint in order to bring up the breakpoint properties dialog to edit the existing breakpoint. +
- Hold the Control key while double-clicking on a location with no breakpoints, in order to bring up the breakpoint properties dialog to create a new breakpoint. +
+Image:The editor gutter popup menu with the hints for the new accelerators. +
+Function Breakpoint Manual Entry
+There is a new option for creating a function breakpoint: +
+- Open the Breakpoints view menu. +
- Select Add Function Breakpoint C/C++. +
- Fill in the function name or expression and select OK to create breakpoint. +
Advanced character encoding support
+CDT now supports the handling of different character encodings for strings and wide character strings while debugging. This includes full support for Unicode encodings and many other popular encodings as well. You can select the character and wide character encoding within the Debug preferences. +
+CDT will then correctly display strings according to the selected encoding while debugging. +
+Note that this feature requires GDB version 7.0 or later. This feature was completed on March 7th, 2012 as part of Bug 307311, Bug 367456 and Bug 370462. +
+Timeout support for GDB commands in DSF/GDB
+Timeouts for GDB commands are now supported in DSF/GDB. The feature is optional and disabled by default. The timeout values are configurable. When the feature is enabled, custom values can be assigned to some commands, all other commands use the default value. This feature was completed on April 17th, 2012 as part of Bug 361934. +
+
+
+
+Multi-select Resume/Suspend operations
+CDT now allows to perform a Resume or Suspend operation on multiple selections of the same debug session. Because such a concept only adds value in a Non-Stop debug session, it is only supported in such a session (see Non-Stop Debugging). The behavior of a multi-selection Resume/Suspend is as follows: +
+- Any selected stack frames implies a selection of their corresponding thread. +
- If one or more threads are selected (not processes) and the resume/suspend operation is triggered, each selected thread on which the operation is currently valid will be resumed/suspended. +
- If one or more processes are selected (not threads) and the resume/suspend operation is triggered, each selected process will be resumed/suspended. Resuming/suspending a process implies resuming/suspending each one of its threads on which the operation is currently valid. +
- If both thread(s) and process(es) are selected, and the resume/suspend operation is triggered, each selected process will be resumed/suspended, and each selected thread which is not part of any selected process will be resumed/suspended. The idea is that if a process is being resumed/suspended, each of its threads will be automatically resumed/suspended, and therefore, should not be resumed/suspended a second time because it is also selected. +
As hinted above, CDT takes a permissive approach to multi-select resume/suspend. This means that if a multi-selection includes both stopped and running threads, a resume operation is still allowed, and only the suspended threads will be resumed; similarly, on such a multi-selection, a suspend operation is allowed, and only the running threads will be suspended. +
+Example
+
+In the above screenshot if the user were to press the Resume button with the current multi-selection the following would happen: +
+- The Consumer process node is selected, therefore the entire process will be resumed. This means that the suspended threads 7 and 9 will be resumed, while threads 6, 8 and 10 will be ignored, as they are already running. +
- Note that the fact that threads 9 and 10 are selected is ignored, as those threads are part of the selected Consumer process, which will be resumed. +
- Stack frames doWork() and work() are selected and belong to thread 4, which becomes implicitly selected in their place. Thread 4 will therefore be resumed. +
- Thread 2 is selected and suspended, and will be resumed. +
- Thread 5 is selected but running, so it will be ignored. +
This feature was completed April 25th, 2012 as part of Bug 330974 +
+Show only suspended threads in Debug view
+CDT now has an global preference that allows to only show the suspended threads within the Debug view. When dealing with a large number of threads, a user is typically interested by the threads that are being inspected (suspended ones) and does not care about the running ones. Using this preference, all running threads will not be shown in the Debug view. Note that when a thread is stepping it will remain visible, although it is technically running. The process element of the Debug view will show how many threads are currently being filtered from view. +
The below example shows the exact same debugging session. The first screenshot only shows suspended threads, while the second shows all threads. +
+
+Below shows how to access the preference, which is disabled by default. +
+This feature was completed May 4th, 2012 as part of Bug 375585 +
+Multi-select attach dialog
+CDT now allows selecting more than one process to attach to in a single user operation. The bottom pane is used to see which processes have been selected. If multi-process debugging is not supported with your debug session (needs GDB >= 7.2 and NonStop enabled), only the first process will be attached to. +
+This feature was completed June 30th, 2011 as part of Bug 293679 +
+Default Postmortem file location
+CDT now allows the user to specify a default directory for the location of core files for a postmortem launch when the prompt is triggered. Since a postmortem launch can easily be re-used for different core files of the same binary, this feature helps reduce the amount of navigation needed to select a core file. Note that specifying the actual core file is still supported, as well as leaving the entire field blank, which will also trigger the prompt, but use the default directory for its starting location. +
Note that this 'core file' field supports the use of variables such as ${workspace_loc}. +
This feature applies to both core files and trace files. +
+This feature was completed on February 17th, 2012 as part of Bug 362039 +
+Support for Fast Tracepoints
+CDT now allows the user of fast tracepoints, as supported by GDB. Fast tracepoints use an instruction jump instead of a trap for efficiency. Fast tracepoint need a minimum of space to be inserted in the program and therefore, may fail to be set at certain locations. For fast tracepoints to work, a special library called the in-process agent (IPA), must be loaded in the inferior process. This library is built and distributed as an integral part of gdbserver. Please see the GDB documentation for more details. +
The user can select between three tracepoint modes in the launch: +
+- Fast: Only use fast tracepoints. No tracepoint will be planted if a fast tracepoint cannot be used. +
- Normal: Only use normal tracepoints. +
- Automatic: Attempt to use fast tracepoints. If a fast tracepoint cannot be used, automatically use a normal tracepoint. +
+This feature was completed July 20th, 2011 as part of Bug 346320 +
+Enhancements to Tracepoints
+With the use of GDB 7.4, some new features are available within Eclipse. +
+- Live enable/disable of C/C++ Tracepoints
+
- Tracepoints can now be enabled and disabled at any time after a trace experiment has been started, and will immediately take effect within the ongoing experiment. +
- Note: Although GDB 7.4 seems to allow a tracepoint to be created during a trace experiment and will add it to the ongoing experiment, this behavior seems to have some issues. One of which is that deleting a tracepoint during an experiment will not remove that tracepoint from the ongoing experiment. Until this is fixed in GDB, it is recommended that the user stick to enable/disable operations during a tracing experiment.
+
- Smaller Fast tracepoints
+
- On 32-bit x86-architectures, fast tracepoints can now be placed at locations with 4-byte instructions, when they were previously limited to locations with instructions of 5 bytes or longer. +
- Tracepoint collecting of Strings
+
- The tracepoint Collect action now has an option to request to collect character pointers as strings. It tells GDB to effectively dereference pointer-to-character types and collect the bytes of memory up to a zero byte. An optional integer limit sets a bound on the number of bytes that will be collected. This feature was completed on April 20th, 2012. For details see Bug 373707 +
+
+
+Show the actual variable type based on RTTI
+With GDB 7.5 or higher CDT could show the actual variable type (not the declared one) in Variables and Expressions Views. Consider the following example: +
+struct SuperInterface { + virtual ~SuperInterface() {} // enable RTTI for Interface class + }; + + struct TheImplementation : public SuperInterface { + TheImplementation(int _v1, float _v2) + : someField(_v1), anotherField(_v2) {} + + int someField; + float anotherField; + }; + + + int main() { + SuperInterface* i = new TheImplementation(42, 4.2); + return 0; // [Launch debug until here] + } ++Launch the debugging session and run until return statement: +
+This feature is enabled by default and will work if you have the proper GDB version (7.5 or higher) and RTTI generation enabled (enabled by default in gcc), however it could be turned off in preferences: +
+This feature was completed on May 5th, 2012 as part of Bug 376901 and Bug 377536. +
+Build variables support in "C/C++ Application" field of launch configuration
+
+There are also a few new CDT-specific build variables: +
+- config_name - the name of the active configuration for the project specified as an argument; +
- config_description - the description of the active configuration for the project specified as an argument; +
This feature was completed on April 2nd, 2012 as part of Bug 180256 and Bug 375814. +
+Support for octal number format in CDI
+CDI now also supports to use the octal number format to display the contents of variables, expressions and registers. You can select the octal number format within the Debug preferences. This feature was completed on March 7th, 2012 as part of Bug 370462. +
+
+C/C++ Unit Testing Support
+
+
+Supported features: +
+- tests running with support of the following frameworks: + +
- tests hierarchy browsing; +
- test messages viewing, filtering by test or test suite; source lookup is also supported; +
- testing statistics (total/failed/aborted tests count, red/green bar); +
- testing time measurement; +
- tests hierarchy filters (show only failed tests); +
- running & rerunning only selected tests (not a whole test module); +
- start a debug session for the whole test module or only the selected tests; +
- test messages filters (by severity); +
- test runs history; +
- the list of provided tests runners may be easily extended writing a new Tests Runner Plugin. +
The HOWTO, known problems and limitation can be found in the CDT FAQ on the wiki. +
This feature was completed April 18th, 2012 as part of Bug 210366. +
+Bugs Fixed in this Release
+Bugzilla tasks completed for this release: + +CDT 8.1 bug fixes +
+ +
+What's new in other CDT releases
+ +To learn what's new in other CDT releases see:
+ + + + + + + + + +
+
- Add Breakpoint action.
+