Community
Participate
Working Groups
The resume() method from org.eclipse.cdt.debug.mi.core.cdi.model.Target [1] could return an exception if the inferior (i.e the process being debugged) is already in running state (i.e not in suspend state). The fix seems easy (only catch this exception) but the strange behaviour is that it occurs only when a debug session is started a second time. I will leave this bug as open until I find the reason get more explanation from someone (may be a cdt guy ?) Does it come from CDT or from gdb attach command itself (but "The first thing GDB does after arranging to debug the specified process is to stop it" [2]) ? more infos : [1] http://www.koders.com/java/fidBAA822FB9978040C467604730F0834F2F96E0F3C.aspx?s=Inferior_already_running#L356 [2] http://www1.jct.ac.il/cc-res/online-doc/gdb/gdb_23.html