Commit r1066661: "Make it possible to run kdevelop in gdb again"

[Andreas Pakulat]

On 28.12.09 12:20:10, David Nolden wrote:
> I think that commit is not good. That way, when you start KDevelop without an 
> argument and a session, two instances of KDevelop wills stay running, one of 
> which wastes at least 100 MB of memory (a duchain repository is always loaded)
> 
> Why is this even required? You can just start KDevelop and then attach to it 
> ("gdb --pid `pidof kdevelop`").

You can't debug startup code that way.
 
> To debug the application startup, we can add a "--nofork" option.

Then one would need to set the session as envvar right? Thats not an
option either.

Andreas

-- 
Your true value depends entirely on what you are compared with.