Community
Participate
Working Groups
You have to disabel an then reenable break points in a shared lib each time you re-start debugging or the break point "fails to install". Break points must be re examined after each shared lib is loaded. -- Configuration Details -- Product: Eclipse 1.3.0.20100617-0520 (org.eclipse.epp.package.cpp.product) Installed Features: org.eclipse.platform 3.6.0.v20100602-9gF78GpqFt6trOGhL60z0oEx3fz-JKNwxPY
Hi Jim, are you using DSF-GDB (in your debug configuration)? If so, take a look at bug 248595. It should work in recent 8.0 builds, you can get a recent build here: http://download.eclipse.org/tools/cdt/builds/8.0.0/index.html If you don't want to change to 8.0 (which is still in development), you could switch to Standard Create Process Launcher (CDI) in your debug configuration.
(In reply to comment #1) > Hi Jim, are you using DSF-GDB (in your debug configuration)? If so, take a look > at bug 248595. It should work in recent 8.0 builds, you can get a recent build > here: > > http://download.eclipse.org/tools/cdt/builds/8.0.0/index.html > > If you don't want to change to 8.0 (which is still in development), you could > switch to Standard Create Process Launcher (CDI) in your debug configuration. Marc, Thanks for the tip. I see this issue has a long history. When I get chance I will try an 8.0 build. Of course, I am use to funky debuggers, and at least I could get the breakpoint, it's if I forgot to disable and re-enable it on a run, it skips the break point all together, so you think it never hit the code...
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). 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 mark the bug as resolved.
