Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-debug-dev] StandAlone CDT debugger (was: Debugging native apps) 
> 
> Most of the native apps I work on already have an existing=20
> build procedure that isn't going to change.=20
> 
> I find that I launch Insight rather than CDT as a debug GUI for these
> projects.
> 
> The reason used to be that Insight worked better + it was easier to
> launch.
> =20
> The biggest hurdle is currently that it is too much hazzle to launch CDT
> for a "tiny debug session". I don't want the whole store, I just want a
> GDB GUI frontend.
> 
> E.g.:
> 
> $ insight --args foo=20
> 
> 
> Q: Doesn't Eclipse support all the infrastructure to allow writing an
> "Eclipse CDT command line wrapper"?
> 
> Essentially this wrapper would:
> 
> - Create an empty dummy CDT project. CDT needs a project to be happy.
> - Create an ephemeral debug session=20
> - Launch debugger
> 
> The ephemeral debug session should be configurable via command line
> options to the "Eclipse CDT command line wrapper"
> 
> 
> Comments?
> 

A few.

> Like?=20
> 

bah!

> Hate? :-)
> 

A lot.  ...  Kidding.


Usually folks talking about this are :
  - GDB users.
  - Unix type users.
  - ..

What they are really saying(what they are complaining about):
  - they want a "light" version, i.e. when starting
    you are not looking at the eclipse icon for 3 minutes before the
    !@^%# main window pops.
  - they have the impression(!) all those plugins and dead weight(CVS/Team, etc ...)
    are slowing them down, hence we just want the debugger,  they want the "strip" version.
    meaning you do not need 1 G. of RAM to be comfortable.
  - the usual complaints ... "I just want to debug my hello_world app, the source is
    right there!! for chr... sake !!
  - ... and please !!! no launch configuration crap, just run/debug the thing!!!!

In other words ... GDB ... but with the bells of CDT/UI, i.e. the dessert bug skipping
the vegetables.

Problems:
-  CDT/Debug lies on top of the Eclipse/Debug platform, which will pull in JFace, Eclipse/UI,
Workbench and all ... CDT/Debug depends also on CDT/{Core, UI}(use of the AST parser and the binary parser).
So it is still "heavy" ...

- Glossing over the need to create a workspace(IFile and all) on the fly. 


Maybe I'm wrong, but I always have the impression that if Eclipse could start within 2 seconds
we would not have this exchange 8-).

Visual Studio can start within 2 seconds and I do not see/hear any requests for "stand-alone" versions.

I have to agree about improving the ease of use, whether with better support autoconf/automake or
better/simpler integration etc ..

Meanwhile, users can:
  - create a project(std make), change the default location to point to the executable and .. debug.
  - or using an existing project, use linked folder/file

Back to the top