| Summary: | Kdevelop crashes on start | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Sergey Vidyuk <sir.vestnik> |
| Component: | Build tools: CMake | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | openprjcfg.crash.bt | ||
|
Description
Sergey Vidyuk
2015-03-31 17:59:16 UTC
Could you help to debug this? I.e. from what revision of kdevplatform/kdevelop did you upgrade? Did you also upgrade KF5? And please install debug symbols for KF5, they're missing. Also see: https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Backtraces Created attachment 91864 [details] openprjcfg.crash.bt I've played with debug printing of pointers values and the issues disappeared (looks like there was stack corruption somewhere). Now I cant reproduce original issue however the same session always crashes on attempt to open project configuration with the stacktrace attached. The session contains two projects: https://github.com/VestniK/lrstar https://github.com/VestniK/meta One more strange thing I see in the logs just before crash: QCoreApplication::postEvent: Unexpected null receiver Thanks for the feedback. Related patch: commit db3e79e01eeea78c8b05828b33914a3c35dd44c5 Author: Kevin Funk <kfunk@kde.org> Date: Wed Jul 9 16:28:29 2014 +0200 CMakeUtils: Protect against null pointers Be more defensive against unexpected input for these functions. 'project' might be 0 in some circumstances => crash. (This happens when quickly shutting down KDevelop after startup) Backtrace: Thread 2 (Thread 0x7fcf81dea700 (LWP 10002)): [KCrash Handler] 5 (anonymous namespace)::baseGroup (project=project@entry=0x0) at /home/krf/devel/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:83 6 0x00007fcf83506c96 in (anonymous namespace)::currentBuildDirIndex (project=project@entry=0x0) at /home/krf/devel/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:98 7 0x00007fcf83506dc0 in (anonymous namespace)::readProjectParameter (project=project@entry=0x0, key=..., aDefault=...) at /home/krf/devel/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:109 8 0x00007fcf83506e42 in CMake::currentBuildDir (project=0x0) at /home/krf/devel/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:254 9 0x00007fcf81f0ce99 in CMakeImportJob::initializeProject (this=this@entry=0x2024cf0, rootFolder=0x42ec130) at /home/krf/devel/src/kdevelop/projectmanagers/cmake/cmakeimportjob.cpp:134 10 0x00007fcf81f0dc43 in CMakeImportJob::initialize (this=0x2024cf0) at Is this still reproducible? Just reproduced this on current 4.7 branch: Thread 8 (Thread 0x7ff75e3c4700 (LWP 13085)): [KCrash Handler] #6 0x00007ff81bbbabd4 in KConfigGroup::config() const () from /usr/lib/libkdecore.so.5 #7 0x00007ff81bbbd087 in KConfigGroup::hasKey(char const*) const () from /usr/lib/libkdecore.so.5 #8 0x00007ff81bbbd2c3 in KConfigGroup::hasKey(QString const&) const () from /usr/lib/libkdecore.so.5 #9 0x00007ff76a61ad47 in (anonymous namespace)::currentBuildDirIndex (project=<optimized out>) at /home/kfunk/devel/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:103 #10 0x00007ff76a619331 in (anonymous namespace)::readProjectParameter (project=0x0, key=..., aDefault=...) at /home/kfunk/devel/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:112 #11 0x00007ff76a6180b2 in CMake::currentBuildDir (project=0x7ff738004a68) at /home/kfunk/devel/src/kdevelop/projectmanagers/cmake/cmakeutils.cpp:261 #12 0x00007ff754aadb04 in CMakeImportJob::initializeProject (this=0x11fdb20, rootFolder=<optimized out>) at /home/kfunk/devel/src/kdevelop/projectmanagers/cmake/cmakeimportjob.cpp:134 #13 0x00007ff754aad786 in CMakeImportJob::initialize (this=<optimized out>) at /home/kfunk/devel/src/kdevelop/projectmanagers/cmake/cmakeimportjob.cpp:119 #14 0x00007ff754aafffd in QtConcurrent::RunFunctionTask<void>::run (this=0x147a8a0) at /usr/include/qt4/QtCore/qtconcurrentrunbase.h:134 #15 0x00007ff81a2ade0a in QThreadPoolThread::run (this=0x114b250) at concurrent/qthreadpool.cpp:108 #16 0x00007ff81a2bae3c in QThreadPrivate::start (arg=0x114b250) at thread/qthread_unix.cpp:352 #17 0x00007ff817df46fa in start_thread (arg=0x7ff75e3c4700) at pthread_create.c:333 #18 0x00007ff8196dcb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. 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 mark the bug 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! 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! |