Bug 210141 - Breakpoints in other projects stop working when debugger is launched
Summary: Breakpoints in other projects stop working when debugger is launched
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 5.0   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: 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: 2007-11-16 15:44 EST by Peter Eastman CLA
Modified: 2020-09-04 15:24 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 Peter Eastman CLA 2007-11-16 15:44:01 EST 
Build ID: M20071023-1652

Steps To Reproduce:
I'm using Eclipse Europa for C++ development on Mac OS X 10.4.10.

My workspace contains several projects, which form a stack.  That is, the second one depends on the first one, the third depends on the first two, etc.  This means that the execution of a single program may involve code in several projects.

When I launch the debugger, any breakpoints in projects *other* than the one the executable is in stop working.  The debugger does not stop at them, and a yellow warning marker appears in the source code next to the line with the message, "Unresolved breakpoint."  If I remove the breakpoint and then set it again, it will work correctly for the rest of that debugging session.  But as soon as I relaunch the debugger, it stops working again.

Breakpoints in the same project as the executable do continue to work across multiple debugging sessions.

More information:
Comment 1 Ken Ryall CLA 2007-11-27 17:42:47 EST 
I made some progress on this but need to do some more work on it. I was hoping to have this fixed for 4.0.2 but I'm going to have to move the milestone to 4.0.3.
Comment 2 Ken Ryall CLA 2008-01-24 01:47:52 EST 
I can no longer reproduce this problem, are you still seeing this? It may have been fixed as a side effect of a recent breakpoint filtering fix.
Comment 3 Peter Eastman CLA 2008-01-24 15:30:59 EST 
Have those changes been released?  I'm using 4.0.2, and it claims there are no updates available.  And yes, I still see this problem.
Comment 4 Ken Ryall CLA 2008-01-24 16:17:22 EST 
Can you turn on verbose console mode and see the traffic with gdb? If you can attach this information it might give me a clue about why the breakpoints are unresolved. I tried a few more projects and still couldn't duplicate this.
Comment 5 Ken Ryall CLA 2008-01-28 17:05:29 EST 
Sorry, I've just now realized you reported this against Mac OS 10.5.1 and I've been trying to reproduce it with 10.4.x. Leopard has a new gdb with it and we probably need to make some adjustments to CDT to account for it. I'll start looking into it tomorrow but I'm moving the milestone to FUTURE as I'm now sure how much we'll have to change.
Comment 6 Jonah Graham CLA 2019-12-30 17:05:15 EST 
This bug was assigned and targeted at a now released milestone. As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and marked the bug as resolved.