Skip to main content
Jump to: navigation, search

Difference between revisions of "CDT/User/NewIn87"

< CDT
(Process exit code shown in execution console title)
(Debug)
Line 31: Line 31:
  
 
== Debug  ==
 
== Debug  ==
 +
 +
=== Exited processes shown in the debug view ===
 +
When debugging multiple processes, when a process would exit on its own, it would simply disappear from the debug view.  This was not very user friendly.  With this release, CDT will keep displaying an exited process in the debug view and will include its exit code.
 +
 +
[[Image:CDT_ExitedProcesses.png]]
 +
 +
To remove entries for exited processes, the user can select one or more of them and then press the Terminate or Disconnect button.  The number of exited processes shown is limited by CDT to avoid filling the view with such entries.
 +
 +
[[Image:CDT_ExitedProcessesRemove.png]]
 +
 +
Another benefit in showing an exited process is that it can be restarted with the ''Restart'' context-menu command.
 +
 +
[[Image:CDT_ExitedProcessRestart.png]]
 +
 +
This feature can also be interesting for single process debugging when un-selecting the preference to kill GDB after the process exits (''Preferences -> C/C++ -> Debug -> GDB -> Terminate GDB when last process exits'').  In this context, the exited process will also be shown to the user and can also be restarted.
 +
 +
This feature was completed through [http://eclip.se/407340 Bug 407340].
  
 
=== Multicore Visualizer ===
 
=== Multicore Visualizer ===

Revision as of 15:27, 1 May 2015

General

Project-less Execution

For a while now CDT has supported debugging a program that was not part of a project. With CDT 8.7, the same can be done when Running a program. What this means is that the user can specify any C/C++ program on the file system in a Run configuration and CDT will execute it.

CDT ProjectLessRun.png

This feature was completed through Bug 464078.

Process exit code shown in execution console title

When a process completes execution normally, its exit code is shown in the title of that process's console. This was provided by CDT since version 8.2 but only for the Debug case. It is now supported for the Run case.

CDT Debug ExitCode.png

This feature was completed through Bug 463975.

Editor

Options for Format with Empty Selection

The Format command (Ctrl+Shift+F) in C/C++ editor can now be configured to format either the whole file or the current statement when no code is selected.

C Editor Preference Page.png

If Ask for confirmation is checked, the command will display a dialog asking user what to do:

Select Formatting Scope Dialog.png

Build

Debug

Exited processes shown in the debug view

When debugging multiple processes, when a process would exit on its own, it would simply disappear from the debug view. This was not very user friendly. With this release, CDT will keep displaying an exited process in the debug view and will include its exit code.

CDT ExitedProcesses.png

To remove entries for exited processes, the user can select one or more of them and then press the Terminate or Disconnect button. The number of exited processes shown is limited by CDT to avoid filling the view with such entries.

CDT ExitedProcessesRemove.png

Another benefit in showing an exited process is that it can be restarted with the Restart context-menu command.

CDT ExitedProcessRestart.png

This feature can also be interesting for single process debugging when un-selecting the preference to kill GDB after the process exits (Preferences -> C/C++ -> Debug -> GDB -> Terminate GDB when last process exits). In this context, the exited process will also be shown to the user and can also be restarted.

This feature was completed through Bug 407340.

Multicore Visualizer

Add persistent information storage

The Multicore Visualizer was enhanced to permit easy persistence of information. The information is saved in the workspace, and can be global for any instance of the view or saved per view.

As part of this change, the state of the load meters is now preserved, per MV view instance.

This feature was completed through Bug 460837.

Make showing debug actions in toolbar configurable

The presence of Debug actions (Resume, Suspend, Step-into, etc) in the Multicore Visualizer toolbar has been previously discussed. Those buttons are "clones" of the platform debug buttons, already present in the main toolbar and optionally in the Debug View toolbar.

By default, the Debug actions are displayed in each MV view toolbar, but can be hidden, using the toggle action from the view menu:

MV-show debug actions in toolbar2.1.png

Debug actions hidden:

MV-show debug actions in toolbar3.png

The user's choice is preserved, per MV view, in the current workspace.

This feature was completed through Bug 460476.

Simplified extensibility for CDT's debug views

For extenders of CDT's debugger (DSF-GDB), we have made it easier to override the behaviour of the debug views. This is made possible by allowing to extend GdbAdapterFactory.java and the new GdbSessionAdapters.java. An example of this can be seen in org.eclipse.cdt.examples.dsf.gdb.

This improvement was completed through Bug 462623.

Bugs Fixed in this Release

See Bugzilla report Bugs Fixed in CDT 8.7

Back to the top