[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 232809] Crash on startup
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2010-03-31 9:54:09
Message-ID: 20100331095409.8ED063C3C9 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=232809





--- Comment #5 from Andreas Pakulat <apaku gmx de>  2010-03-31 11:54:06 ---
(In reply to comment #4)
> I have a glibc bugfix update, but that should be there already for a month, so
> not recent. I compiled gdb cvs from source lately, if that could affect it...

No, that shouldn't affect this. I was more thinking of the libc bug wrt. the
malloc-check code being not threadsafe. The standard backtrace with that bug
occurred from free going through 3 or 4 functions in libc before ending in
raise/abort. And your backtrace looked similar enough to double-check.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]