Community
Participate
Working Groups
Created attachment 186878 [details] Fix DSF-GDB supports both all-stop and non-stop mode. However, there is currently no easy way for different services to find out which mode is being used by the debug session. The below fix adds method getRunMode() to IMIRunControl. I tried to make the RunMode concept easy to extend for debuggers that may have some mode other than all-stop or non-stop.
Pawel, this changes seems to me like it would fit quite well in DSF itself. Ken, is this something you want for EDC? The current patch is for DSF-GDB, but I can create an IRunControl3 if you want to have this change in DSF. If not, I'll commit the change to DSF-GDB early next week. Thanks
Committed the patch to HEAD. Pawel, can you review?
*** cdt cvs genie on behalf of mkhouzam *** Bug 334463: [run control] Need a way to know if we are in non-stop mode [*] MIRunControl.java 1.30 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/MIRunControl.java?root=Tools_Project&r1=1.29&r2=1.30 [*] IMIRunControl.java 1.7 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/IMIRunControl.java?root=Tools_Project&r1=1.6&r2=1.7 [*] GDBRunControl_7_0_NS.java 1.26 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBRunControl_7_0_NS.java?root=Tools_Project&r1=1.25&r2=1.26