Help to understand/fix Kdevelop Crash

Milian Wolff mail at
Thu Apr 23 14:39:23 UTC 2015

On Saturday 18 April 2015 15:00:31 Lucas Tanure wrote:
> On Apr 18, 2015 1:40 PM, "Milian Wolff" <mail at> wrote:
> > On Saturday 18 April 2015 16:27:37 Lucas Tanure wrote:
> > > Hi,
> > > 
> > > The version of Linux doesn't matter, any version that I used got the
> same
> > > behavior.
> > 
> > Will a release tarball do? Do I need to run configure or anything to get
> > Makefiles generated, or is every setup in such a tarball already?
> Jus git clone the Linus tree over
> Clean tree, do not run make config or anything else.
> Maybe a tarball from Linux source it's good too.
> > > I import as a project with Makefile. When the parse gets 50% of all
> files
> > > parsed the crash happens, more or less 4gb used of ram. I compiled
> > > kdevelop, kdev-clang on debug mode.
> > 
> > Did you need to setup any custom include paths or similar stuff? Or
> should it
> > crash even without this?
> Nope, just git Clone and import.
> We could talk over Google Hangouts or Skype, I really want this working,
> but I don't understand the kdevelop and kdev-clang source.

I just tried it today and it worked just fine... Everything is the latest 
master version and for Linux I used the official 4.0 tarball and imported the 
top-level Makefile.

One thing I noticed is that the progress bar doesn't make much sense. It 
approaches 50% and then just jumps directly to 100%. Something to investigate.

In general, it's certainly relatively slow (~15min or so on my beefy machine) 
and does not leverage the available CPUs as nicely as I'd hoped it would. In 
the future, I'll try to optimize KDevelop a bit more for this usecase.

Milian Wolff
mail at

More information about the KDevelop-devel mailing list