Bug 356488 - [breakpoints] Thread filter don't work with GDB 7.0 or 7.1
Summary: [breakpoints] Thread filter don't work with GDB 7.0 or 7.1
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-09-01 11:35 EDT by Marc Khouzam CLA
Modified: 2020-09-04 15:21 EDT (History)
3 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-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.