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

Bug 356488

Summary: [breakpoints] Thread filter don't work with GDB 7.0 or 7.1
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, john, pawel.1.piech
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Marc Khouzam CLA 2011-09-01 11:35:43 EDT
From Bug 349736 comment 12:

"When I use GDB 7.0 or 7.1, I get:

   ctxt:       gdb[1].proc[42000].threadGroup[42000]
   context:    gdb[1].proc[].threadGroup[]

This is a problem I ran into before in Bug 336890.  But I missed the scenario
of thread filters.  I'm surprised your ctxt variable has the 42000 threadGroup
and proc set...

All this works properly with GDB >= 7.2, but apparently no so much with olders
GDBs."

This situation makes using thread filters completely deactivate a breakpoint.  The reason is that the threadGroupId is not set when we first create a breakpoint, but it is set when we first set the thread filter.  Since the two contexts don't match, the breakpoint is not installed on any threads.