Bug 206105

Summary: kdevelop crash KDevelop::allocateRepository: KDevelop::ItemRepositoryRegistry::open
Product: [Applications] kdevelop Reporter: tomwardathome
Component: generalAssignee: kdevelop-bugs-null
Status: RESOLVED DUPLICATE    
Severity: crash CC: d.scheftelowitsch, fyanardi
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description tomwardathome 2009-09-03 13:49:26 UTC 
Application that crashed: kdevelop
Version of the application: 3.9.95 (using KDevPlatform 0.9.95)
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-9-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
Ubuntu 9.10 updated , 2nd Spetember 2009
can't start kdevelop

tt2tjw@tt2tjw-shed:~$ kdevelop
WARNING: deleting stale lockfile /home/tt2tjw/.kdevduchain/1/lock
<unknown program name>(24475)/ KDevelop::allocateRepository: picked duchain directory "/home/tt2tjw/.kdevduchain/1"
<unknown program name>(24475)/ KDevelop::ItemRepositoryRegistry::open: version-hint not found, seems to be an old version 
<unknown program name>(24475)/ KDevelop::ItemRepositoryRegistry::open: "The data-repository at /home/tt2tjw/.kdevduchain/1 has to be cleared." 
<unknown program name>(24475)/ KDevelop::allocateRepository: picked duchain directory "/home/tt2tjw/.kdevduchain/1"
KCrash: Application 'kdevelop' crashing...
sock_file=/home/tt2tjw/.kde/socket-tt2tjw-shed/kdeinit4__0



 -- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
[KCrash Handler]
#5  _int_malloc (av=0x7f3a560a9e40, bytes=112) at malloc.c:4404
#6  0x00007f3a55db975e in *__GI___libc_malloc (bytes=112) at malloc.c:3638
#7  0x00007f3a5617564d in operator new(unsigned long) () from /usr/lib/libstdc++.so.6
#8  0x00007f3a56604cd6 in QImageData::create (size=<value optimized out>, format=QImage::Format_ARGB8565_Premultiplied, numColors=0) at image/qimage.cpp:226
#9  0x00007f3a566052bb in QImage (this=0x7fffc431fca0, width=16, height=16, format=QImage::Format_ARGB8565_Premultiplied) at image/qimage.cpp:831
#10 0x00007f3a56605b2b in QImage::copy (this=0x7fffc431fea0, r=<value optimized out>) at image/qimage.cpp:1397
#11 0x00007f3a56605f4b in QImage::detach (this=0x7fffc431fea0) at image/qimage.cpp:1353
#12 0x00007f3a56607015 in QImage::bits (this=0x7fffc431fea0) at image/qimage.cpp:1841
#13 0x00007f3a575918f5 in KIEImgEdit (img=<value optimized out>, col=..., value=<value optimized out>) at ../../kdeui/icons/kiconeffect.cpp:310
#14 KIconEffect::colorize (img=<value optimized out>, col=..., value=<value optimized out>) at ../../kdeui/icons/kiconeffect.cpp:378
#15 0x00007f3a57c518e0 in WorkingSet (this=<value optimized out>, id=<value optimized out>, icon=<value optimized out>) at ../../shell/workingsetcontroller.cpp:654
#16 0x00007f3a57c5456d in KDevelop::WorkingSetController::getWorkingSet (this=0x33d5020, id=) at ../../shell/workingsetcontroller.cpp:130
#17 0x00007f3a57c551f5 in WorkingSetController (this=0x33d5020, core=<value optimized out>) at ../../shell/workingsetcontroller.cpp:82
#18 0x00007f3a57c736fc in KDevelop::CorePrivate::initialize (this=0x33d2da0, mode=KDevelop::Core::Default) at ../../shell/core.cpp:96
#19 0x00000000004079df in _start ()

Reported using DrKonqi
Comment 1 Andreas Pakulat 2009-09-03 14:13:50 UTC 
Does it help if you remove $HOME/.kdevduchain?
Comment 2 Dimitri Scheftelowitsch 2009-10-08 12:20:52 UTC 
I confirm this behaviour with the latest openSUSE builds. Removing $HOME/.kdevduchain as well as swtching to a newer Qt development snapshot (20091005) does not help.
Comment 3 Fredy Yanardi 2009-10-30 17:15:53 UTC 
I also get exactly the same crash and backtrace, with Qt 4.6, kdelibs + kdevelop from trunk.

What I've tried so far:
* Running kdevelop 3.9.94 and 3.9.95 packaged by debian + Qt 4.5 + kdelibs 4.3.0
* Upgrade glibc from 2.9 to 2.10.1
* Running kdevelop from trunk.
* Removing ~/.kdevduchain
Comment 4 Andreas Pakulat 2009-10-30 19:06:18 UTC 
Ah, this also seems to be another incarnation of the libc 2.10 update. I'm personally quite convinced that this really shows a bug in the new libc's malloc-checking. I can't believe that Qt code is that broken all over the place to trigger all these crashes.

*** This bug has been marked as a duplicate of bug 206775 ***