Bug 198953 - kdevelop crashes when trying to open an already opened (cmake) project a second time
Summary: kdevelop crashes when trying to open an already opened (cmake) project a seco...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: CMake (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-07-04 21:47 UTC by Oliver Putz
Modified: 2018-10-21 05:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
bt full log for crash from bug 198953 (26.99 KB, text/plain)
2009-07-04 21:49 UTC, Oliver Putz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Putz 2009-07-04 21:47:45 UTC
Version:           3.9.93 (using KDevPlatform 0.9.93) (using 4.2.4 (KDE 4.2.4), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.28-gentoo-r6

Steps to reproduce:

1) Open a (cmake) project in kdevelop
2) Close kdevelop
3) Go to Project -> Open Recent and select the first project
4) Repeat step 3 (wait a little if you get the error message that the project is currently being opened and thus not being opened a second time)
5) Click yes when being asked to repoen the current project
6) See kdevelop crash with the following backtrace

#0  QHash<QString, QStringList>::duplicateNode (node=0x7c10b, newNode=0x7f419080dea0) at /usr/include/qt4/QtCore/qstring.h:711
#1  0x00007f41b19b0645 in QHashData::detach_helper (this=0x7f41a0c42bc0, node_duplicate=0x7f418ef53dc0 <QHash<QString, QStringList>::duplicateNode(QHashData::Node*, void*)>, 
    nodeSize=<value optimized out>) at tools/qhash.cpp:207
#2  0x00007f418ef5594b in VariableMap::insert (this=0x7f41a0c3ddd8, varName=@0x7f418eab7e20, value=<value optimized out>) at /usr/include/qt4/QtCore/qhash.h:568
#3  0x00007f418ef432b9 in CMakeProjectVisitor::visit (this=0x7f418eab97a0, exec=0x7f4190d429c0)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1199
#4  0x00007f418ef49a66 in CMakeProjectVisitor::walk (this=0x7f418eab97a0, fc=@0x7f4190b5ac80, line=6, isClean=false)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1972
#5  0x00007f418ef4e89a in CMakeProjectVisitor::visit (this=0x7f418eab97a0, ifast=0x7f4190b5ac70)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1138
#6  0x00007f418ef49a66 in CMakeProjectVisitor::walk (this=0x7f418eab97a0, fc=@0x7f41a03c3810, line=5, isClean=false)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1972
#7  0x00007f418ef4e89a in CMakeProjectVisitor::visit (this=0x7f418eab97a0, ifast=0x7f41a03c3800)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1138
#8  0x00007f418ef49a66 in CMakeProjectVisitor::walk (this=0x7f418eab97a0, fc=@0x7f41a044faa0, line=2, isClean=false)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1972
#9  0x00007f418ef4e89a in CMakeProjectVisitor::visit (this=0x7f418eab97a0, ifast=0x7f41a044fa90)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1138
#10 0x00007f418ef49a66 in CMakeProjectVisitor::walk (this=0x7f418eab97a0, fc=@0x7f418eab9a30, line=0, isClean=true)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/parser/cmakeprojectvisitor.cpp:1972
#11 0x00007f418f197c13 in CMakeManager::includeScript (this=0xa06cab0, file=@0x7f418eab9d40, project=0x5c6ef20, parent={m_topContext = 0x7f418eab9d30})
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/cmakemanager.cpp:394
#12 0x00007f418f19b6fa in CMakeManager::initializeProject (this=0xa06cab0, project=0x5c6ef20, baseUrl=@0x7f41908c8b78)
    at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/cmakemanager.cpp:291
#13 0x00007f418f1a15a0 in CMakeManager::parse (this=0xa06cab0, item=0x7f41904b95f0) at /var/tmp/portage/dev-util/kdevelop-3.9.93/work/kdevelop-3.9.93/projectmanagers/cmake/cmakemanager.cpp:442
#14 0x00007f41aeebba3c in KDevelop::ImportProjectJobPrivate::import (this=0x7f4190160d20, folder=0x7f419080dea0)
    at /var/tmp/portage/dev-util/kdevplatform-0.9.93/work/kdevplatform-0.9.93/project/importprojectjob.cpp:47
#15 0x00007f41aeebb8a6 in QtConcurrent::RunFunctionTask<void>::run (this=0x7f41902ff520) at /usr/include/qt4/QtCore/qtconcurrentrunbase.h:120
#16 0x00007f41b19897cc in QThreadPoolThread::run (this=0x8158650) at concurrent/qthreadpool.cpp:106
#17 0x00007f41b19918d9 in QThreadPrivate::start (arg=0x8158650) at thread/qthread_unix.cpp:189
#18 0x00007f41b1721017 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#19 0x00007f41aff9f48d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#20 0x0000000000000000 in ?? ()
Comment 1 Oliver Putz 2009-07-04 21:49:26 UTC
Created attachment 35049 [details]
bt full log for crash from bug 198953

A yet more verbose log for this crash. If any other info is needed, just ask
Comment 2 Andreas Pakulat 2009-07-04 22:41:23 UTC
the verbose log looks like a complete stack corruption. I'll try to reproduce it.
Comment 3 Andreas Pakulat 2009-07-05 23:05:36 UTC
I can't reproduce this. To rule out one common reason (these days) of weird crashes deep inside Qt: Oliver which glibc are you using?
Comment 4 Oliver Putz 2009-07-06 00:21:14 UTC
Hi! My currently installed glibc version is:

sys-libs/glibc-2.9_p20081201-r2

And even though I can recompile kdevelop, I also assume that its no miscompilation as I use only -O2. So no overly agressive compilation flags either.

In any case, as perhaps my description was lacking something important to make the crash reproducible for you, I uploaded a video on how to reproduce the crash at 
http://www.oliver-putz.de/bugreports/bug198953.ogv

If any more information is needed: Just ask again.
Comment 5 Andrew Crouthamel 2018-09-19 04:30:43 UTC
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!
Comment 6 Andrew Crouthamel 2018-10-21 05:00:59 UTC
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!