Bug 281325 - Lack of consistency between "Debug As" menu and "Debug Configurations"
Summary: Lack of consistency between "Debug As" menu and "Debug Configurations"
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 0 DD 1.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-24 05:00 EDT by Toralf Lund CLA
Modified: 2020-09-04 15:22 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Lund CLA 2009-06-24 05:00:34 EDT
Build ID:  M20080911-1700

Steps To Reproduce:
1. In a C/C++ project, select Run->Debug As...
2. Select Run->Debug Configurations...
3. Compare the two...


More information:
I'm not sure if this is a "bug" or "feature request", but I would expect to see more consistent lists of debug types in the two "views" indicated above.

In the "Debug Configurations..." menu I have 3 configuration types that are specific to C/C++ applications:
C/C++ Attach To Local Application
C/C++ Local application
C/C++ Postmortem debugger

The "Debug As" submenu, on the other hand, has only:
Local C/C++ application

This seems to indicate that the two are independently configured (notice how the one type that is duplicated doesn't even have the same name.) I believe it would be a better design not to have a separate setup for "Debug As", but instead let the menu automatically pick up configuration types from "Debug Configurations..."

On a more practical level, I would *really* like to have a "postmortem debugger" and "attach to local application" in the debug menu - especially the former. I often want to do a quick check of a coredump from a program I'm not working with on a daily basis, which today means having to add a new debug configuration every time. This is a bit too cumbersome, IMO.
Comment 1 Pawel Piech CLA 2009-06-24 13:40:03 EDT
(In reply to comment #0)
> On a more practical level, I would *really* like to have a "postmortem
> debugger" and "attach to local application" in the debug menu - especially the
> former. I often want to do a quick check of a coredump from a program I'm not
> working with on a daily basis, which today means having to add a new debug
> configuration every time. This is a bit too cumbersome, IMO.

This is good input, thank you.  How do you imagine "attach to local application" may work from the "Debug As..." menu?  Shouldn't it really be contributed to a view that shows running processes (e.g. RSE view)?
Comment 2 Toralf Lund CLA 2009-06-25 03:56:10 EDT
(In reply to comment #1)
> (In reply to comment #0)
> > On a more practical level, I would *really* like to have a "postmortem
> > debugger" and "attach to local application" [ ... ]
> 
> This is good input, thank you.  How do you imagine "attach to local
> application" may work from the "Debug As..." menu?  Shouldn't it really be
> contributed to a view that shows running processes (e.g. RSE view)?

Good question.

The most obvious use would perhaps be to access "Debug As..." via the "right-click" menu of a binary listed in the Project Explorer. In that case, the program and configuration type are both known, so the operation may be exactly like for a pre-existing debug configuration with that combination.

If the program is not known, one might always ask the user for it fist of all, before continuing "as usual" and request the process, but it would probably be more convenient to be able to select both in one go. Ideally, a popup listing the subset of running processes that correspond to programs known by Eclipse should be used for this.

But yes, adding the ability to start a debug connection to an existing view of running processes also sounds like a good idea.