Re: [cdt-debug-dev] Projectless debugging of Linux apps

["Alain Magloire" <alain@xxxxxxx>]

> 
> >> Unleash CDT! Remove the check for whether a binary is inside a CDT
> >> project!
> >
> > I think the better way is to add a special launch configuration,
> > at least for now.
> 
> I want to understand why you say this, because I think it essentially
> kills all hope of making baby-steps towards projectless debugging.
> 
> It seems to me that the Eclipse CDT team prefers large atomic
> contributions over small improvements. I can see why, but those
> contributions are much rarer and much less likely unless some sponsor
> steps.
> 

Actually it is the opposite, as the large pool of contributors
to the CDT can attest.  Your patches, in the past, were rejected
or accepted on technical merits.

Now stick to the technical discussion.

> This is particularly frustrating since CDT actually does work with
> projectless local debugging as well or better than Insight in many
> cases, with a couple of restraining bolts removed.
> 
> While I'm at it, I'd also like to understand why these "restraining
> bolts" are put into the code in the first place.
> 

Eclipse has a certain workflow and the launch is the usual
way to run/debug applications.  Not everything can fit
in the local launch and having a specific launch is an avenue
we can explore.

They are still some unanswered questions, like how to provide
persistency for breakpoints, source locators, which binary parser to
use, when an external file is brought in the CEditor what information
to give to the source parser(Macros, include paths), do we expect normal
navigation(F3) to work, are actions like search enable  etc ... since
this launch will not be tied to any project.