Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#98 Pressing the 'debug' icon in C/C++ perspective opens 'Launch Debug Configuration Selection'

Next release
closed
None
5
2014-10-14
2014-03-24
Stephen Davey
No

Hi,

My name is Stephen Davey and I work with John Moule at Somnium Technologies. I understand you have already had some contact with John recently.

I'm reporting a bug related to the GNU ARM plugins for Eclipse Kepler. It concerns pressing the Debug icon from within the C/C++ Debug perspective. Now if there is a GNU ARM based project selected in the Project Explorer (see attached screenshot - project_selected.png) then instead of the last debug launch being launched, the 'Launch Debug Configuration Selection' dialog is opened (see screenshot - launch_debug.png).

Pressing the same debug icon , but without a project being selected under the Project Explorer (after closing and reopening the Project Explorer) or when selected a resource from within a project under the Project Explorer, then the last debug is launched, as expected.

Pressing the debug icon from within the Debug perspective also behaves as expected - the last debug is launched.

I hope this is sufficient to help you reproduce the behaviour. However, let me know if anything is not clear.

Thanks

Stephen

2 Attachments

Discussion

    • status: open --> open-accepted
    • assigned_to: Liviu Ionescu (ilg)
     
  • hi Stephen, thank you for the bug report. this is a known problem of Eclipse CDT, the behaviour is the same with other debug plug-ins too.

    I'll try to investigate if a workaround in the plug-in is possible, otherwise the CDT bug needs to be addressed.

     
    Last edit: Liviu Ionescu (ilg) 2014-03-24
  • Stephen Davey
    Stephen Davey
    2014-03-24

    Hi Liviu,

    Thanks for your reply.

    I don't know if this helps, but I didn't see this problem in a Kepler SR1 installed on my Linux machine, with a native C/C++ project setup with a debug launch configured to launch native GDB. I has no GNU ARM plugins installed under this Kepler install.

    Thanks

    Stephen

     
  • please try the GDB Hardware Debugging plug-in, with the DSF configuration, and let me know if the problem is also present.

     
  • Stephen Davey
    Stephen Davey
    2014-03-25

    Hi Liviu,

    I've just tried a new Workspace with only a GDB Hardware Debugging launch set up. I see the same issue.

    Cheers

    Stephen

     
  • thank you, this is consistent with my tests and confirms my opinion that we face a CDT DSF bug.

     
  • Stephen Davey
    Stephen Davey
    2014-03-25

    I agree - I'll look through the CDT list of issues to see if this is already known and if not I'll raise a bug.

    Thanks for your help.

     
  • ok. if you identify any workaround that we can apply in the plug-in, just let me know and we'll try to implement it.

     
  • Good to know.

    If you could attach a patch there, it might speed up things.

     
    Last edit: Liviu Ionescu (ilg) 2014-05-19
  • John Moule
    John Moule
    2014-05-19

    Indeed! I'm playing around with an idea at the moment that might fix it.

     
  • As Marc commented, perhaps there is something that we can add to the plug-ins in order to avoid that behaviour, otherwise the patches pushed via Gerrit might take quite some time to be accepted.

     
  • John Moule
    John Moule
    2014-05-21

    That might be possible. From Marc's comments it may be possible to correctly hook into the debug button using <extension point="org.eclipse.debug.ui.launchShortcuts">.

    I'll have another look at it sometime, but I'm on another task right now.
    cheers john

     
  • I'll have another look

    ok, if you find a local fix, I'll evaluate and include it in the plug-ins.

     
    • status: open-accepted --> open-postponed
     
    • status: open-postponed --> open-accepted
     
  • I added the following preference in the debug plug-in and the behaviour changed, the last used debug configuration is now used:

    org.eclipse.debug.ui/org.eclipse.debug.ui.UseContextualLaunch=false

     
  • John Moule
    John Moule
    2014-10-11

    nice find. Searching it seems some people put that in their product's plugin_customization.ini. I'll experiment with it.

     
    • status: open-accepted --> closed
     
  • fixed in 2.4.1-201410142110, by changing the default using a preference definition