Summary: | kdevelop crash KDevelop::allocateRepository: KDevelop::ItemRepositoryRegistry::open | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | tomwardathome |
Component: | general | Assignee: | 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
Does it help if you remove $HOME/.kdevduchain? 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. 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 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 *** |