Bug 166354 - crash while opening a (cmake) project
Summary: crash while opening a (cmake) project
Status: RESOLVED DUPLICATE of bug 167283
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-12 10:08 UTC by David Solbach
Modified: 2008-09-29 10:24 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Solbach 2008-07-12 10:08:43 UTC
Version:           SVN revision 828802 (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.3.1 
OS:                Linux

I worked on a cmake project and then closed the application.
Afterwards I started kdevelop (rev 828802) again. It showed all the files I had opened when I closed kdevelop but it didn't seem to have the project itself loaded up (no Projects Tab on the left side).

Then I went to File->Close all Others which worked fine.
In the next Step I Chose Project->Open Recent->[the project I worked on].

Loading the project produced the crash. I hope the attached backtrace helps.

-- Backtrace --

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f37e2eb8700 (LWP 4440)]
[New Thread 0x408f6950 (LWP 4449)]
[New Thread 0x42fe4950 (LWP 4442)]
[New Thread 0x427e3950 (LWP 4441)]
[KCrash handler]
#4  0x00007f37db134d1d in qobject_cast<KTextEditor::SmartInterface*> (
    object=0x405cd70) at /opt/kde4/include/ktexteditor/smartinterface.h:505
#5  0x00007f37db134250 in KDevelop::DocumentRangeObject::range (this=0x4054700)
    at /home/david/Projects/kde/src/KDE/kdevplatform/language/editor/documentrangeobject.cpp:156
#6  0x00007f37d11fb8db in ClassModel::filterObject (this=0xbe8fb0, 
    object=0x4054700)
    at /home/david/Projects/kde/src/KDE/kdevplatform/plugins/classbrowser/classmodel.cpp:110
#7  0x00007f37d11fbd85 in ClassModel::refreshNode (this=0xbe8fb0, 
    node=0x29f93c0, base=0x4054700, resultChildren=0x7fffeaeffe30)
    at /home/david/Projects/kde/src/KDE/kdevplatform/plugins/classbrowser/classmodel.cpp:377
#8  0x00007f37d11fc7e1 in ClassModel::branchModified (this=0xbe8fb0, context=
        {d = {d = 0x7fffeaefff20}})
    at /home/david/Projects/kde/src/KDE/kdevplatform/plugins/classbrowser/classmodel.cpp:513
#9  0x00007f37d11fcaaf in ClassModel::qt_metacall (this=0xbe8fb0, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x4055300)
    at /home/david/Projects/kde/build/KDE/kdevplatform/plugins/classbrowser/classmodel.moc:75
#10 0x00007f37e02819ce in QObject::event () from /usr/lib64/libQtCore.so.4
#11 0x00007f37dc25292d in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#12 0x00007f37dc258cfa in QApplication::notify () from /usr/lib64/libQtGui.so.4
#13 0x00007f37e13f2c2a in KApplication::notify (this=0x7fffeaf00c30, 
    receiver=0xbe8fb0, event=0x30529a0)
    at /home/david/Projects/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311
#14 0x00007f37e0273e9c in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#15 0x00007f37e02747cb in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib64/libQtCore.so.4
#16 0x00007f37e029a590 in QEventDispatcherUNIX::processEvents ()
   from /usr/lib64/libQtCore.so.4
#17 0x00007f37dc2d334a in ?? () from /usr/lib64/libQtGui.so.4
#18 0x00007f37e02727f2 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#19 0x00007f37e0272985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#20 0x00007f37e0274a25 in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#21 0x0000000000407038 in main (argc=1, argv=0x7fffeaf01b98)
    at /home/david/Projects/kde/src/KDE/kdevelop/src/main.cpp:209
Comment 1 Andreas Pakulat 2008-09-29 10:24:42 UTC

*** This bug has been marked as a duplicate of bug 167283 ***