Bug 101841 - race condition in CBreakpointUpdater causes breakpoints not to be set on all targets
Summary: race condition in CBreakpointUpdater causes breakpoints not to be set on all ...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 2.1.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-27 05:31 EDT by Hampus Edvardsson CLA
Modified: 2020-09-04 15:26 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 Hampus Edvardsson CLA 2005-06-27 05:31:58 EDT 
I have extended CDT to launch a configuration consisting of multiple targets.
This works fine, but when I set a breakpoint on a source line that is available
for all targets, the breakpoint is sometimes fail to be set for all targets.

The code first sets the breakpoint on all Targets. After this, depending on the
timing, it sometimes remove the breakpoint from one of the contexts.

This behaviour seems to be caused by a thread synch bug in the
CBreakpointUpdater in CDT.
Comment 1 Nobody - feel free to take it CLA 2005-07-11 17:14:55 EDT 
Can you try it with the latest build? Major changes have made in 
CBreakpointManager in RC2 to prevent the UI blocking.
Comment 2 Daniel Friederich CLA 2009-09-18 19:49:25 EDT 
I've added bug 289915.
I'm not sure, but this could eventually be the same bug. This bug is quite old and there have been a few changes since. 
However the description 
"The code first sets the breakpoint on all Targets. After this, depending on the
timing, it sometimes remove the breakpoint from one of the contexts."
matches the issue I fixed in bug 289915.