Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Trace Compass/News/NewIn12"
(→Support for Filtering of Kernel Events) |
|||
| Line 1: | Line 1: | ||
| − | = Support for LTTng session profiles = | + | = LTTng Control view enhancements = |
| + | == Support for LTTng session profiles == | ||
| − | == Saving of LTTng session profiles == | + | === Saving of LTTng session profiles === |
It is now possible to save a LTTng session from the '''LTTng Control''' view. The session configuration will be saved as profile in the user's workspace and can be used later on to load this session back on a node where LTTng 2.5 or later is installed. | It is now possible to save a LTTng session from the '''LTTng Control''' view. The session configuration will be saved as profile in the user's workspace and can be used later on to load this session back on a node where LTTng 2.5 or later is installed. | ||
[[Image:SaveSessionConfigAction.png]] | [[Image:SaveSessionConfigAction.png]] | ||
| − | == Loading of LTTng session profiles == | + | === Loading of LTTng session profiles === |
The '''LTTng Control''' now supports loading one or more previously saved LTTng session configuration from the LTTng Control view. Using the Load session dialog box is possible to select the session profile to load. | The '''LTTng Control''' now supports loading one or more previously saved LTTng session configuration from the LTTng Control view. Using the Load session dialog box is possible to select the session profile to load. | ||
[[Image:LoadSessionConfig.png]] | [[Image:LoadSessionConfig.png]] | ||
| − | == Managing of LTTng session profiles == | + | === Managing of LTTng session profiles === |
A new preference page has been added to manage LTTng session profiles stored in the user's workspace. It is now possible to share profiles using the the import and export features as well as it is possible to delete a profile from the workspace. | A new preference page has been added to manage LTTng session profiles stored in the user's workspace. It is now possible to share profiles using the the import and export features as well as it is possible to delete a profile from the workspace. | ||
[[Image:ManageSessionConfig.png]] | [[Image:ManageSessionConfig.png]] | ||
| − | = Support for filtering of kernel events = | + | == Support for filtering of kernel events == |
The LTTng '''Control''' view implementation now supports filtering of kernel events when enabling kernel events which was added for LTTng v2.7.0 runtime. | The LTTng '''Control''' view implementation now supports filtering of kernel events when enabling kernel events which was added for LTTng v2.7.0 runtime. | ||
Revision as of 11:54, 15 January 2016
Contents
LTTng Control view enhancements
Support for LTTng session profiles
Saving of LTTng session profiles
It is now possible to save a LTTng session from the LTTng Control view. The session configuration will be saved as profile in the user's workspace and can be used later on to load this session back on a node where LTTng 2.5 or later is installed.
Loading of LTTng session profiles
The LTTng Control now supports loading one or more previously saved LTTng session configuration from the LTTng Control view. Using the Load session dialog box is possible to select the session profile to load.
Managing of LTTng session profiles
A new preference page has been added to manage LTTng session profiles stored in the user's workspace. It is now possible to share profiles using the the import and export features as well as it is possible to delete a profile from the workspace.
Support for filtering of kernel events
The LTTng Control view implementation now supports filtering of kernel events when enabling kernel events which was added for LTTng v2.7.0 runtime.
Support for filtering in Resources view
The Resources view now supports filtering of resources such as CPUs, IRQs and soft-IRQs.
Persistent filter in Control Flow and Resources view
The filter settings of Control Flow and Resources view are now persisted for all open traces. Switching between open traces won't remove the filter settings of each trace.
Support for refreshing of local traces
It is now possible to refresh traces from the Project Explorer and Events Table using a menu option of the F5 key. The trace index of updated traces will resume and the table will show added events.
Trace indexing improvement
The indexing operation of traces and experiment will resume when closing and reopening a trace before the initial indexing operation was finished.
Bugs fixed in this release
See Bugzilla report Bugs Fixed in Trace Compass 1.2