Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349968 - [tracepoints] Decorator for active tracepoints
Summary: [tracepoints] Decorator for active tracepoints
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-21 13:38 EDT by Marc Khouzam CLA
Modified: 2020-09-04 15:26 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Khouzam CLA 2011-06-21 13:38:40 EDT 
GDB tracepoints are created like breakpoints, but are only actually activated once the tracing experiment is started.  If a new tracepoint is created while the tracing experiment is running, that new tracepoint will not be part of the current experiment.

Therefore, it would be nice to have a decorator to show the user that a tracepoint is actively being used in a trace experiment right now.

Furthermore, when starting a trace experiment, some tracepoints may not become active; for example, a fast tracepoint may fail to get installed on a particular target.  Having an 'active' decorator would indicate to the user that a particular breakpoint was not made active.  Some error hover message would be nice also in that case.

Multi-target tracepoint don't play well with this decorator as an 'active' tracepoint won't indicate for which target it is active.  The 'enhanced breakpoint support' feature of the multicore debug workgroup will help with this.