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

David Nolden zwabel at
Mon Dec 28 11:20:10 UTC 2009

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`").

To debug the application startup, we can add a "--nofork" option.

Greetings, David

More information about the KDevelop-devel mailing list