Community
Participate
Working Groups
This may be a dupe, but seems a major out-of-the box regression from CDI. I've got a bunch of breakpoints in some source files that exist in a .so. CDI correctly sets these when it detects the .so is loaded, while DSF doesn't. The result is I haven't figure out (out the box anyway) how to use DSF to debug my app. GNU gdb (GDB) 7.0.1 CDT: 2010-05-01 19:09:26
Created attachment 170047 [details] CDI MI log - breakpoints are set
Created attachment 170048 [details] DSF MI log - breakpoints not set
Sorry James, this is one of the parity bugs we didn't have time to get too. The fix (GDB >= 6.8) is not very big, but the handling of the breakpoint marker was not trivial and I ran out of time. *** This bug has been marked as a duplicate of bug 248595 ***
Ok, thanks Marc
If you want to try a hack to make your life easier, you can make the below two character change in org.eclipse.cdt.dsf.mi.service.command.commands.MIBreakInsert I think this will make your breakpoints on shared libs work. public MIBreakInsert(IBreakpointsTargetDMContext ctx, boolean isTemporary, boolean isHardware, String condition, int ignoreCount, String location, int tid, boolean disabled, boolean isTracepoint) { - super(ctx, "-break-insert"); //$NON-NLS-1$ + super(ctx, "-break-insert -f"); //$NON-NLS-1$