Bug 355403 - [tracepoints] When available, show thread Id in trace visualization
Summary: [tracepoints] When available, show thread Id in trace visualization
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-22 11:11 EDT by Marc Khouzam CLA
Modified: 2020-09-04 15:22 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-08-22 11:11:11 EDT 
From bug 347514 comment 16:

It would be nice for the user to see on what thread the data was originally collected, i.e., which thread hit the tracepoint.  I don't believe GDB 7.2 has a way to collect this information.  However, I know there was a requested enhancement to have a trace state variable for the thread id, that the user would be able to collect.  If that variable is collected, we could be smart about it and show it in the debug view.

I'm not sure which GDB version will have this enhancement.  Maybe 7.3?

The enhancement description states:
"add support to record a thread identifier. This shall be the raw thread identifier as provided by the system. If a user-visible name is available, it shall be supported (for instance PR_SET_NAME). This shall be specified by a trace state variable, and must be collected by user action (either explicitly or default) in order to be available."