Community
Participate
Working Groups
As a developer debugging multiple processes on the same target system I would like to see them grouped together in the debug view even if they are created when I launch them separately. Otherwise the debug view becomes very confusing. The root of this problem is that the debug platform treats a launch as both a verb and a noun. It is both a set of actions that may create one or more contexts on a target system and the results of those actions. Since the debug view shows launches as the root elements of the view this leads to a confusing display when you have multiple launches that create debug contexts on the same target system. For example, if you launch a debug session for a windows executable and get a process as the result, then launch another one, people expect to see them grouped together in the view, not shown as separately as different launches. One attempt to address this is in bug 281587, which adds a new view. But until the platform has better support for this, EDC can make some interim improvements: The EDC launch delegate now has a way for subclasses to say that a launch configuration is targeting the same target system as an existing launch and then reuse the existing launch instead of creating a new one. The existing DSF session is also reused. This will give people something more like the desired user experience.
Created attachment 173673 [details] round one Support multiple source locators for an EDC launch, support reusing an existing DSF session. Preliminary support in the Windows debugger.
*** cdt cvs genie on behalf of kryall *** Bug 319151 - Multi launch improvements [*] LinuxX86LaunchDelegate.java 1.5 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.linux.x86/src/org/eclipse/cdt/debug/edc/linux/x86/launch/LinuxX86LaunchDelegate.java?root=Tools_Project&r1=1.4&r2=1.5 [+] Messages.properties http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/src/org/eclipse/cdt/debug/edu/internal/ui/sourcelookup/Messages.properties?root=Tools_Project&revision=1.1&view=markup [+] Messages.java http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/src/org/eclipse/cdt/debug/edu/internal/ui/sourcelookup/Messages.java?root=Tools_Project&revision=1.1&view=markup [+] InstructionPointerImageProvider.java http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/src/org/eclipse/cdt/debug/edu/internal/ui/sourcelookup/InstructionPointerImageProvider.java?root=Tools_Project&revision=1.1&view=markup [+] InstructionPointerManager.java http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/src/org/eclipse/cdt/debug/edu/internal/ui/sourcelookup/InstructionPointerManager.java?root=Tools_Project&revision=1.1&view=markup [+] SourceLookupResult.java http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/src/org/eclipse/cdt/debug/edu/internal/ui/sourcelookup/SourceLookupResult.java?root=Tools_Project&revision=1.1&view=markup [+] EDCSourceDisplayAdapter.java http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/src/org/eclipse/cdt/debug/edu/internal/ui/sourcelookup/EDCSourceDisplayAdapter.java?root=Tools_Project&revision=1.1&view=markup [*] MANIFEST.MF 1.8 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/META-INF/MANIFEST.MF?root=Tools_Project&r1=1.7&r2=1.8 [*] EDCAdapterFactory.java 1.11 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/src/org/eclipse/cdt/debug/edc/ui/EDCAdapterFactory.java?root=Tools_Project&r1=1.10&r2=1.11 [*] plugin.xml 1.24 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.ui/plugin.xml?root=Tools_Project&r1=1.23&r2=1.24 [*] WindowsFinalLaunchSequence.java 1.15 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.windows/src/org/eclipse/cdt/debug/edc/windows/launch/WindowsFinalLaunchSequence.java?root=Tools_Project&r1=1.14&r2=1.15 [*] WindowsLaunchDelegate.java 1.5 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.windows/src/org/eclipse/cdt/debug/edc/windows/launch/WindowsLaunchDelegate.java?root=Tools_Project&r1=1.4&r2=1.5 [*] SnapshotLaunchDelegate.java 1.6 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc/src/org/eclipse/cdt/debug/edc/internal/launch/SnapshotLaunchDelegate.java?root=Tools_Project&r1=1.5&r2=1.6 [*] CSourceLookup.java 1.5 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc/src/org/eclipse/cdt/debug/edc/internal/launch/CSourceLookup.java?root=Tools_Project&r1=1.4&r2=1.5 [*] ServicesLaunchSequence.java 1.7 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc/src/org/eclipse/cdt/debug/edc/internal/launch/ServicesLaunchSequence.java?root=Tools_Project&r1=1.6&r2=1.7 [*] EDCLaunch.java 1.14 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc/src/org/eclipse/cdt/debug/edc/launch/EDCLaunch.java?root=Tools_Project&r1=1.13&r2=1.14 [*] AbstractFinalLaunchSequence.java 1.34 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc/src/org/eclipse/cdt/debug/edc/launch/AbstractFinalLaunchSequence.java?root=Tools_Project&r1=1.33&r2=1.34 [*] EDCLaunchDelegate.java 1.12 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc/src/org/eclipse/cdt/debug/edc/launch/EDCLaunchDelegate.java?root=Tools_Project&r1=1.11&r2=1.12 [*] Stack.java 1.24 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc/src/org/eclipse/cdt/debug/edc/services/Stack.java?root=Tools_Project&r1=1.23&r2=1.24
Ken, could you document the new method in AbstractCLaunchDelegate2? I would really like to see us improve our documentation practices going forward. In this case AbstractCLaunchDelegate2 is API, and it really shouldn't have *any* undocumented methods. Going back and documenting everything is a heavy request, but I think it's fair to ask that we be diligent with all new API.
(this is part of a batch change) The Eclipse CDT EDC (https://wiki.eclipse.org/CDT/cdt-debug-edc) is now obsolete and has not had any active development since 2011. Therefore the still open bugs are being marked as wontfix. The git repo for the project still exists for posterity at https://git.eclipse.org/c/cdt/org.eclipse.cdt.edc.git/
