Help to understand/fix Kdevelop Crash

[Lucas Tanure]

On Apr 18, 2015 12:52 PM, "Milian Wolff" <mail at milianw.de> wrote:
>
> Hey All!
>
> On Tuesday 17 March 2015 13:22:05 David Nolden wrote:
> > Actually, the absolute limit on the size of the item repository is 4GB,
> > because the index is a 32 bit number, and there can be 1<<16 buckets,
each
> > of size 1<<16, i.e. 1<<32=4.3GB. Maybe this limit is hit in your case.
Can
> > you add some assertion which avoids "wrapping" of the bucket number
> > (especially of the buckets spanned by the "monster bucket extent")?
> >
> > However, that limit applies to each item repository separately. In your
> > case it seems to be the persistent symbol table. IMO it should never
become
> > that huge, not even for the linux kernel. So I guess this is a problem
in
> > kdevelop-clang, which puts too much stuff in the symbol table (just a
> > guess).
>
> I think this is a very good guess. I've seen similar problems before in
kdev-
> clang and that should certainly be investigated. Kevin, you added some
tooling
> around the item repositories recently, no? Can we see what gets added to
the
> symbol table and what not?
>
> Also, Lucas - you marked https://bugs.kde.org/show_bug.cgi?id=343950 as a
> duplicate but say here it's actually not. So should I un-mark it and keep
it
> open?

Yes keep open. I really think that is the same bug, because the stack trace
is the same.

I bought more ram for me, but the issue is still happening.
I would like that kdev-clang save on the hard drive the parsing output,
because it's not good to reparse the files every time.

Thanks

>
> Bye
>
> > 2015-03-15 2:15 GMT+01:00 Lucas Tanure <tanure at linux.com>:
> > > Hi,
> > >
> > > I'm trying to use kdevelop for develop linux kernel, but it's crashing
> > > while parsing.
> > > I imported the main makefile from linux kernel source and after a few
> > > minutes the kdevelop crashes.
> > >
> > > Take a look at:
> > > *kdevelop* *binaries* :
> > > https://www.dropbox.com/s/g01t1uzpkkwihwt/kdevelop.tar.xz?dl=0
> > >
> > > *llvm* *binaries* :
> > > https://www.dropbox.com/s/j8xarqu6leufk8s/llvm.tar.xz?dl=0
> > >
> > > *kdevelop* *log* :
https://www.dropbox.com/s/ke4iovxx8alis9j/kdev.log?dl=0
> > >
> > > *gdb* *coredump* :
> > > https://www.dropbox.com/s/1q7l8pi67kug59r/core.24956.xz?dl=0
> > >
> > > I created the bug:
> > > https://bugs.kde.org/show_bug.cgi?id=343950
> > >
> > > and I thought it was the same as:
> > > https://bugs.kde.org/show_bug.cgi?id=272408 ( not enough memory ram ).
> > > But it's not, it's a real crash. I tested with a 24Gbytes of Ram, and
> > > kdevelop took like 5Gb to parse 50% of linux kernel.
> > >
> > > Please help.
> > > Thanks
> > >
> > > --
> > > Lucas Tanure
> > > +55 (19) 988176559
> > >
> > > _______________________________________________
> > > KDevelop-devel mailing list
> > > KDevelop-devel at kde.org
> > > https://mail.kde.org/mailman/listinfo/kdevelop-devel
>
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20150418/005d0684/attachment.html>