#51 Support programmatic Debug Configuration creation

Time Permitting
closed-fixed
None
5
2014-07-12
2014-06-10
John Moule
No

I would like to generate Debug Configurations programmatically. I'm written some code which is fairly like this:

org.eclipse.cdt.debug.internal.ui.launch.CApplicationLaunchShortcut.createConfiguration()

Note, I can't use that code directly because I can't find the debuggerID of the segger and openocd TabDebugger pages; I don't think they are set up in the same way.

Anyway, I call the ilg.gnuarmeclipse.debug.gdbjtag.jlink.ui.TabDebugger.setDefaults(ILaunchConfigurationWorkingCopy) method simply by instantiating a TabDebugger, writing to the config, saving the config and then I can throw away the TabDebugger. But I notice that only a small part of setDefaults is executed because its "commented out".

The same applies to other setDefaults I need:
ilg.gnuarmeclipse.debug.gdbjtag.jlink.ui.TabStartup.setDefaults(ILaunchConfigurationWorkingCopy)
ilg.gnuarmeclipse.debug.gdbjtag.openocd.ui.TabDebugger.setDefaults(ILaunchConfigurationWorkingCopy)
ilg.gnuarmeclipse.debug.gdbjtag.openocd.ui.TabStartup.setDefaults(ILaunchConfigurationWorkingCopy)

Is there a reason for this? Would it be possible to reinstate those values in setDefaults?

cheers john

Discussion

    • status: open --> open-accepted
    • assigned_to: Liviu Ionescu (ilg)
     
  • I restored the full content of setDefaults(). However, for the functionality of the plug-ins, it is useless, since performApply() always rewrites the configuration values.

    On the other side, I'm not sure your method to initialise a configuration is ok (but I have no arguments for this).

     
  • fixed in 2.3.1-201407120554

     
    • status: open-accepted --> closed-fixed