Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 349967

Summary: [tracepoints] Decorator for fast tracepoints
Product: [Tools] CDT Reporter: Marc Khouzam <marc.khouzam>
Component: cdt-debug-dsf-gdbAssignee: Project Inbox <cdt-debug-dsf-gdb-inbox>
Status: NEW --- QA Contact: Jonah Graham <jonah>
Severity: normal    
Priority: P3 CC: cdtdoug, pawel.1.piech
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Marc Khouzam CLA 2011-06-21 13:32:31 EDT 
Some tracepoints can be installed as 'slow' tracepoints (using traps like breakpoints), while others can be 'fast' tracepoints (using code patching and jumps).

It would be nice to have a visual indicator like a decorator to show the user if the tracepoint is a fast tracepoint or a slow one.  

The way I'm planning on supporting fast tracepoint in bug 346320 is that a tracepoint will be fast or slow, for a specific launch/target.  Therefore, the same tracepoint could be fast for one launch while slow for another.  This complicates the adding of a decorator because we don't handle multi-target breakpoints/tracepoints well at this time.

Say I launch a session which installs a tp as a fast tracepoint.  We add a decorator that shows the fact that it is a fast tp.  If I then launch another session, but that this new session installs the tp as a slow tracepoint, it will no longer be clear from the decorator if the tp is a fast or a slow one.

Once we have 'enhanced breakpoint support' as we have been discussing in the multicore debug workgroup, we should be able to address this issue better.