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/NewIn86"
(Created page with "== Build == == Indexing == == Refactoring == == Debug == == General == == Bugs Fixed in this Release == See Bugzilla report [https://bugs.eclipse.org/bugs/buglist.cgi?...") |
(→Debug) |
||
Line 6: | Line 6: | ||
== Debug == | == Debug == | ||
+ | |||
+ | === Pinning of Multicore Visualizer view === | ||
+ | |||
+ | CDT now supports the pinning of Multicore Visualizer views. A "pin view to debug session" toggle button was added to the Multicore Visualizer, that permits pinning a MV to the current debug session. | ||
+ | |||
+ | A Multicore Visualizer, when pinned, will continue showing the debug session it's pinned-on, even if another debug session is selected in the Debug view. Pinning can be used in conjunction with Multicore Visualizer view cloning, to setup a workspace where multiple MVs are present, each one persistently assigned to a specific debug session. | ||
+ | |||
+ | Here we have a workbench with 2 Multicore Visualizers views. There are 2 ongoing debug sessions in the Debug view; session 2 is selected, and shown in both MVs. Note that the new "pin" button is highlighted in the first MV: | ||
+ | |||
+ | [[Image:mv-pinning-1-highlight.png]] | ||
+ | |||
+ | We switch to session 1, and both MVs follow: | ||
+ | [[Image:mv-pinning-2.png]] | ||
+ | |||
+ | We pin the first MV to session 1 | ||
+ | [[Image:mv-pinning-3.png]] | ||
+ | |||
+ | We switch to debug session 2; pinned MV stays on session 1 | ||
+ | [[Image:mv-pinning-4.png]] | ||
+ | |||
+ | |||
+ | This feature was completed August 22nd, 2014 through [http://eclip.se/441713 Bug 441713]. | ||
== General == | == General == |
Revision as of 15:14, 26 August 2014
Contents
Build
Indexing
Refactoring
Debug
Pinning of Multicore Visualizer view
CDT now supports the pinning of Multicore Visualizer views. A "pin view to debug session" toggle button was added to the Multicore Visualizer, that permits pinning a MV to the current debug session.
A Multicore Visualizer, when pinned, will continue showing the debug session it's pinned-on, even if another debug session is selected in the Debug view. Pinning can be used in conjunction with Multicore Visualizer view cloning, to setup a workspace where multiple MVs are present, each one persistently assigned to a specific debug session.
Here we have a workbench with 2 Multicore Visualizers views. There are 2 ongoing debug sessions in the Debug view; session 2 is selected, and shown in both MVs. Note that the new "pin" button is highlighted in the first MV:
We switch to session 1, and both MVs follow:
We pin the first MV to session 1
We switch to debug session 2; pinned MV stays on session 1
This feature was completed August 22nd, 2014 through Bug 441713.
General
Bugs Fixed in this Release
See Bugzilla report Bugs Fixed in CDT 8.6