Summary: | Kdevelop crashed during scheduled project reparsing | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Vadym Krevs <vkrevs> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Vadym Krevs
2010-01-22 11:39:41 UTC
(In reply to comment #0) > What I was doing when the application crashed: > Kdevelop rebuilt from SVN this morning. Scheduled a project for reparsing. > Closed and restarted Kdevelop (why is this necessary - cannot there be a button > on the toolbar to kick off reparsing???). Kdevelop started reparsing. I left it > alone and decided to get a cup of coffee. When I came back 10 min later, > Kdevelop crashed. FYI, I'm running with > MALLOC_CHECK_=3 so glibc will not try to workaround bad pointers. Instead it'll simply crash because of a race condition in exactly that error-checking code. See the original report for a link to the sourceware bugreport and ask your distro to fix their libc packages. *** This bug has been marked as a duplicate of bug 206775 *** glibc-2.10.1-10.4.x86_64 shipped with opensuse 11.2 already contains the fix from the sourceware bugreport as it was an opensuse developer who implemented it. Yet kdevelop still crashes (and is the only KDE 4.x application that crashes regularly). (In reply to comment #2) > glibc-2.10.1-10.4.x86_64 shipped with opensuse 11.2 already contains the fix Where/How can I see that? I've tried to find a changelog of the patches that SuSE applied to this package, but the ones I found didn't mention the related upstream bug. > from the sourceware bugreport as it was an opensuse developer who implemented > it. Yet kdevelop still crashes (and is the only KDE 4.x application that > crashes regularly). In the upstream libc it was comitted for 2.11.1, so SuSE would need to have backported it and as I said I can't find a trace of that. That said one of the kdev developers also hits the crash, even when unsetting MALLOC_CHECK_ variable. He said that his libc is 2.11.1 and the source is equal to upstream, he tries to track down where exactly it crashes inside libc for him. And on a last note: If it were a bug in KDevelop which the malloc-check uncovers, you wouldn't see the abort from inside the malloc_printerr as far as I understood the libc code. If you unpack the glibc source rpm for opensuse 11.2 (ftp://ftp5.gwdg.de/pub/opensuse/source/distribution/11.2/repo/oss/suse/src/glibc-2.10.1-10.4.src.rpm), you will find the glibc-2.10-mcheck-free-race.diff patch which is identical to the one in glibc's bugzilla. |