Summary: | Crash with autocompletion for C++ include directive | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Ludger Sprenker <Ludger> |
Component: | kdecore | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck, kde-bugs |
Priority: | NOR | Keywords: | triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Ludger Sprenker
2010-01-20 10:40:45 UTC
I've just noticed, that the previous include directive was not closed correctly (missing "-character). Maybe this can help to find the bug. While the crash occurred, the code looked as follows ('X' is the cursor position): #ifndef _ASDF_HPP #define _ASDF_HPP #include "first.hpp #include "seconX" ... Do you have a self-built KDE on your system? I'm asking because its strange that you have debug symbols for some of the kdecore code, but not the template instantiation of QMap. Also can you reproduce this repeating the steps that lead to it the first time? No, KDE is not self-build. I am using kubuntu beta packages from launchepad. Maybe I have only installed debug packages for kdelibs and not for Qt. The bug was not directly reproduceable. But after a while I've just had another crash while editing include directives: Thread 1 (Thread 0xb7874ac0 (LWP 10843)): [KCrash Handler] #6 QBasicAtomicInt::ref (this=0xbfadc78c, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120 #7 QByteArray::operator= (this=0xbfadc78c, other=...) at tools/qbytearray.cpp:865 #8 0x003c0822 in KEntryMap::setEntry(QByteArray const&, QByteArray const&, QByteArray const&, QFlags<KEntryMap::EntryOption>) () from /usr/lib/libkdecore.so.5 #9 0x003d0501 in KConfigIniBackend::parseConfig (this=0x14603308, currentLocale=..., entryMap=..., options=..., merging=false) at ../../kdecore/config/kconfigini.cpp:261 #10 0x003d19e6 in KConfigIniBackend::parseConfig (this=0x14603308, currentLocale=..., entryMap=..., options=...) at ../../kdecore/config/kconfigini.cpp:66 #11 0x003b92cc in KConfigPrivate::parseGlobalFiles (this=0x8e94fe0) at ../../kdecore/config/kconfig.cpp:484 #12 0x003ba484 in KConfig::reparseConfiguration (this=0x8eb1670) at ../../kdecore/config/kconfig.cpp:451 #13 0x002b2f6e in KDevelop::Project::projectConfiguration (this=0x8d92430) at /home/dvelop/src/kdevplatform/shell/project.cpp:480 #14 0x021d8cf6 in CMake::currentBuildDir (project=0x8d92430) at /home/dvelop/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:121 #15 0x05a58811 in CMakeManager::buildDirectory (this=0x8d820c8, item=0x8f0e970) at /home/dvelop/src/kdevelop/projectmanagers/cmake/cmakemanager.cpp:162 #16 0x02b6ed21 in IncludePathComputer::computeForeground (this=0x146e67a0) at /home/dvelop/src/kdevelop/languages/cpp/includepathcomputer.cpp:85 #17 0x02b66cef in CppLanguageSupport::findIncludePathsForJob (this=0x9bed140, job=0xa33155e8) at /home/dvelop/src/kdevelop/languages/cpp/cpplanguagesupport.cpp:393 #18 0x02b6bb19 in CppLanguageSupport::qt_metacall (this=0x9bed140, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0xa2f924d0) at /home/dvelop/src/kdevelop/build/languages/cpp/cpplanguagesupport.moc:142 #19 0x00b0911a in QMetaObject::metacall (object=0x9bed140, cl=149508088, idx=13, argv=0xa2f924d0) at kernel/qmetaobject.cpp:237 #20 0x00b13856 in QMetaCallEvent::placeMetaCall (this=0x9f1c5eb8, object=0x9bed140) at kernel/qobject.cpp:574 #21 0x00b148ae in QObject::event (this=0x9bed140, e=0x9f1c5eb8) at kernel/qobject.cpp:1260 #22 0x043b119c in QApplicationPrivate::notify_helper (this=0x8a20d18, receiver=0x9bed140, e=0x9f1c5eb8) at kernel/qapplication.cpp:4242 #23 0x043b7df7 in QApplication::notify (this=0xbfadd5a0, receiver=0x9bed140, e=0x9f1c5eb8) at kernel/qapplication.cpp:3661 #24 0x03d9267a in KApplication::notify (this=0xbfadd5a0, receiver=0x9bed140, event=0x9f1c5eb8) at ../../kdeui/kernel/kapplication.cpp:302 #25 0x00b03eab in QCoreApplication::notifyInternal (this=0xbfadd5a0, receiver=0x9bed140, event=0x9f1c5eb8) at kernel/qcoreapplication.cpp:704 #26 0x00b068e3 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x89f86e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #27 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x89f86e0) at kernel/qcoreapplication.cpp:1345 #28 0x00b06a4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #29 0x0446f94f in QCoreApplication::sendPostedEvents (this=0x8a20cd8, flags=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #30 QEventDispatcherX11::processEvents (this=0x8a20cd8, flags=...) at kernel/qeventdispatcher_x11.cpp:75 #31 0x00b024c9 in QEventLoop::processEvents (this=0xbfadd4c4, flags=) at kernel/qeventloop.cpp:149 #32 0x00b0291a in QEventLoop::exec (this=0xbfadd4c4, flags=...) at kernel/qeventloop.cpp:201 #33 0x00b06b0f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #34 0x043b1237 in QApplication::exec () at kernel/qapplication.cpp:3570 #35 0x0804dd13 in main (argc=1, argv=0xbfaddaf4) at /home/dvelop/src/kdevelop/app/main.cpp:209 Thanks, thats the same problem probably. Seems like something broke in KConfig. Created attachment 40735 [details]
New crash information added by DrKonqi
Error continues to exist in KDevelop 3.9.98.
This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED) Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |