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

Bug 355403

Summary:	[tracepoints] When available, show thread Id in trace visualization
Product:	[Tools] CDT	Reporter:	Marc Khouzam <marc.khouzam>
Component:	cdt-debug-dsf-gdb	Assignee:	Project Inbox <cdt-debug-dsf-gdb-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	enhancement
Priority:	P3	CC:	cdtdoug, pawel.1.piech
Version:	8.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Marc Khouzam

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."