Re: [cdt-debug-dev] StandAlone CDT debugger (was: Debugging native apps)

[Douglas Schaefer <dschaefe@xxxxxxxxxx>]

cdt-debug-dev-admin@xxxxxxxxxxx wrote on 01/06/2005 01:50:39 PM:

> >>>>> "Alain" == Alain Magloire <alain@xxxxxxx> writes:
> 
> Alain> What they are really saying(what they are complaining about):
> Alain>   - they want a "light" version, i.e. when starting
> Alain>     you are not looking at the eclipse icon for 3 minutes before 
the
> Alain>     !@^%# main window pops.
> 
> FWIW, I'm not so sure the issue is eclipse's speed or perceived
> bloat, but rather the idea that using eclipse at all means figuring
> out how to set up a project, importing the sources, etc...
> 
> In my experience, folks who want this feature seem to be coming from
> an Insight/DDD background.  They just want to point the debugger GUI
> at their executable and source tree and start debugging.
> 
> There's also a kind of command-line user interface issue here, namely
> that you can run "insight foo.exe" and have something useful happen,
> but there's no way to do this with eclipse -- instead you have to do
> some setup before you can start.
> 
> I think that's subtly different from what you're saying.  Personally I
> would find this occasionally useful, but I can completely understand
> why it hasn't been a priority.  It seems like a fair amount of work
> for a kind of corner case (though I realize others don't see it as a
> corner case at all).

That's certainly what it sounds like to me as well. While I think 
supporting such a mode would be valuable for a number of CDT users it does 
come at a pretty significant cost. There is the technical aspect to make 
sure the current workflows aren't disturbed to make it happen. But also, 
who has the resources to do it? All the ideas and votes in bugzilla are 
great and appreciated, but without someone stepping up to do the work... 
Sounds like another great topic over a beverage in SF.

D