Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/User/NewIn92"
(→Display GDB thread ids in the Multicore Visualizer) |
m (→Display GDB thread ids in the Multicore Visualizer) |
||
| Line 41: | Line 41: | ||
=== Display GDB thread ids in the Multicore Visualizer === | === Display GDB thread ids in the Multicore Visualizer === | ||
| − | The Multicore Visualizer shows all threads of the | + | The Multicore Visualizer shows all threads of the process(es) being debugged. Previously, each thread would be represented by a dot followed by the OS thread id of that thread (PID on Linux). |
With this enhancement, the GDB thread id is also displayed, making it easier for the user to map the threads in the Visualizer to the threads in the Debug View and in the Debugger Console. | With this enhancement, the GDB thread id is also displayed, making it easier for the user to map the threads in the Visualizer to the threads in the Debug View and in the Debugger Console. | ||
Revision as of 08:54, 2 November 2016
Contents
Release
This is the New & Noteworthy page for CDT 9.2 which is part of the Eclipse Neon.2 update release of December 2016
General
Editor
Makefile Editor
Code Analysis
Parser
Support for C++14 constexpr evaluation
C++14 expanded the scope of what's allowed inside a constexpr function, to allow variable declarations and most control statements such as loops. CDT now supports evaluation of constexpr functions that make use of these features.
In this example, CDT simulates the execution of a constexpr function that contains a for loop to determine that the type of x is integer<10>.
Formatter
Build
Debug
Full GDB console
This feature was completed through Bug xxxxx.
Display GDB thread ids in the Multicore Visualizer
The Multicore Visualizer shows all threads of the process(es) being debugged. Previously, each thread would be represented by a dot followed by the OS thread id of that thread (PID on Linux).
With this enhancement, the GDB thread id is also displayed, making it easier for the user to map the threads in the Visualizer to the threads in the Debug View and in the Debugger Console.
This feature was completed through Bug 501006.
Bugs Fixed in this Release
See Bugzilla report Bugs Fixed in CDT 9.2