Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "CDT/User/NewIn83"

< CDT
(Debug)
(Debug)
Line 25: Line 25:
  
 
=== Support for multi-process debugging in Memory views ===
 
=== Support for multi-process debugging in Memory views ===
 
 
The Memory view and Memory Browser view now support multi-process debugging.  Beyond properly refreshing their content based on the currently selected process, the user can now define different memory addresses to look at for each process being debugged.  This work was a contribution from Alvaro Sanchez-Leon on January 15th, 2014.  For details see [http://eclip.se/250323 Bug 250323].
 
The Memory view and Memory Browser view now support multi-process debugging.  Beyond properly refreshing their content based on the currently selected process, the user can now define different memory addresses to look at for each process being debugged.  This work was a contribution from Alvaro Sanchez-Leon on January 15th, 2014.  For details see [http://eclip.se/250323 Bug 250323].
 +
 +
=== Detection of target disconnection ===
 +
When doing remote debugging, if the connection to the target is lost, the debug session will be cleanly terminated.  Previously, some situations could lead to a debug session that lost its connection but remained active using the host machine instead; these cases have been fixed. For details see [http://eclip.se/250323 Bug 250323]
 +
 +
=== Basic support of Multicore Visualizer in all-stop mode ===
 +
Previously, the Multicore Visualizer simply was not supported in all-stop mode.  Now, it displays properly in all-stop, with all its features available when the program is suspended, while still updating thread creation/termination when the program is running.
  
 
== Bugs Fixed in this Release  ==
 
== Bugs Fixed in this Release  ==
  
 
See bugzilla report [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;resolution=FIXED;target_milestone=8.2.1;target_milestone=8.2.2;target_milestone=8.2.3;target_milestone=8.3.0;product=CDT;classification=Tools Bugs Fixed in CDT 8.3]
 
See bugzilla report [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;resolution=FIXED;target_milestone=8.2.1;target_milestone=8.2.2;target_milestone=8.2.3;target_milestone=8.3.0;product=CDT;classification=Tools Bugs Fixed in CDT 8.3]

Revision as of 17:32, 15 January 2014

Editor

Build

Toolchains

  • Language dialect options in GNU toolchain definition (Bug 404913).

DialectLanguageStandard.png

Scanner Discovery/Language Settings Providers

  • Use applicable options (such as language dialect) from build settings during discovery of built-in settings (Bug 404913). But note that to use options changed by user the built-in settings provider needs to be set as non-shared.

BuiltInDetectors-FLAGS.png

Indexing

Preferences for header variants

New indexer preferences:

  • Index all header variants
  • Index all header variants of specific headers

IndexerHeaderVariantsPref.png

These new preferences give the user more control over how the indexer handle variants of headers. By default, the indexer will index all variants of headers which do not have include guards or #pragma once. In certain cases, this strategy is not sufficient. To resolve this, the indexer can be configured to index all variants of headers, at the possible expense of indexing time. If the problematic headers are known, a comma separated list of headers can be specified and only those will be indexed for all variants.

Debug

Support for multi-process debugging in Memory views

The Memory view and Memory Browser view now support multi-process debugging. Beyond properly refreshing their content based on the currently selected process, the user can now define different memory addresses to look at for each process being debugged. This work was a contribution from Alvaro Sanchez-Leon on January 15th, 2014. For details see Bug 250323.

Detection of target disconnection

When doing remote debugging, if the connection to the target is lost, the debug session will be cleanly terminated. Previously, some situations could lead to a debug session that lost its connection but remained active using the host machine instead; these cases have been fixed. For details see Bug 250323

Basic support of Multicore Visualizer in all-stop mode

Previously, the Multicore Visualizer simply was not supported in all-stop mode. Now, it displays properly in all-stop, with all its features available when the program is suspended, while still updating thread creation/termination when the program is running.

Bugs Fixed in this Release

See bugzilla report Bugs Fixed in CDT 8.3

Back to the top