Bug 206569 - Crash when quitting when program is being run
Summary: Crash when quitting when program is being run
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: abbreviation plugin (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 209536 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-09-07 01:30 UTC by Ben Boeckel
Modified: 2009-10-06 01:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Boeckel 2009-09-07 01:30:28 UTC
Application that crashed: kdevelop
Version of the application: 3.9.95 (using KDevPlatform 0.9.95)
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30.5-32.fc11.x86_64 x86_64
Distribution: "Fedora release 11 (Leonidas)"

What I was doing when the application crashed:
When a program is running and KDevelop is closed, KDevelop crashes.

 -- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fbe70aac820 (LWP 31354))]

Thread 2 (Thread 0x7fbe67d1d910 (LWP 31355)):
#0  0x00000035d3a0b57d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00000034c345ad62 in QWaitConditionPrivate::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#3  0x00000034ca8c70ee in KDevelop::DUChainPrivate::CleanupThread::run (this=0x203c570) at /usr/src/debug/kdevplatform-0.9.94.20090827svn1016363/language/duchain/duchain.cpp:280
#4  0x00000034c3459d45 in QThreadPrivate::start (arg=0x203c570) at thread/qthread_unix.cpp:188
#5  0x00000035d3a0686a in start_thread () from /lib64/libpthread.so.0
#6  0x00000035d2ede3bd in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fbe70aac820 (LWP 31354)):
[KCrash Handler]
#5  0x0000000000000000 in ?? ()
#6  0x00000034c52eddee in qDeleteAll<QList<KJob*>::const_iterator> (end=<value optimized out>, begin=<value optimized out>) at /usr/include/QtCore/qalgorithms.h:350
#7  qDeleteAll<QList<KJob*> > (end=<value optimized out>, begin=<value optimized out>) at /usr/include/QtCore/qalgorithms.h:358
#8  KCompositeJobPrivate::~KCompositeJobPrivate (end=<value optimized out>, begin=<value optimized out>) at /usr/src/debug/kdelibs-4.3.0/kdecore/jobs/kcompositejob.cpp:29
#9  0x00000034c52eea0a in KJob::~KJob (this=0x1c94c70, __in_chrg=<value optimized out>) at /usr/src/debug/kdelibs-4.3.0/kdecore/jobs/kjob.cpp:69
#10 0x00000034c7a13d53 in KDevelop::ExecuteCompositeJob::~ExecuteCompositeJob (this=0x1c94c70, __in_chrg=<value optimized out>)
    at /usr/src/debug/kdevplatform-0.9.94.20090827svn1016363/util/executecompositejob.cpp:47
#11 0x00000034c354d8bc in QObjectPrivate::deleteChildren (this=0x1f88900) at kernel/qobject.cpp:1847
#12 0x00000034c3555e10 in QObject::~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:836
#13 0x00000034c768b6ed in KDevelop::RunController::~RunController (this=0x1f8af70, __in_chrg=<value optimized out>)
    at /usr/src/debug/kdevplatform-0.9.94.20090827svn1016363/shell/runcontroller.cpp:333
#14 0x00000034c76667cc in KDevelop::CorePrivate::~CorePrivate (this=0x1d1c110, __in_chrg=<value optimized out>) at /usr/src/debug/kdevplatform-0.9.94.20090827svn1016363/shell/core.cpp:202
#15 0x00000034c766696f in KDevelop::Core::~Core (this=0x1d1bf50, __in_chrg=<value optimized out>) at /usr/src/debug/kdevplatform-0.9.94.20090827svn1016363/shell/core.cpp:240
#16 0x00000034c354eb75 in QObject::event (this=0x1d1bf50, e=0x454bec0) at kernel/qobject.cpp:1094
#17 0x00000034c478f69c in QApplicationPrivate::notify_helper (this=0x1c2c360, receiver=0x1d1bf50, e=0x1fbee30) at kernel/qapplication.cpp:4056
#18 0x00000034c47968fe in QApplication::notify (this=0x7fff63167b30, receiver=0x1d1bf50, e=0x1fbee30) at kernel/qapplication.cpp:4021
#19 0x00000034c5a11296 in KApplication::notify (this=0x7fff63167b30, receiver=0x1d1bf50, event=0x1fbee30) at /usr/src/debug/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#20 0x00000034c353f59c in QCoreApplication::notifyInternal (this=0x7fff63167b30, receiver=0x1d1bf50, event=0x1fbee30) at kernel/qcoreapplication.cpp:610
#21 0x00000034c35401a2 in QCoreApplication::sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#22 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1247
#23 0x00000034c3567cc3 in QCoreApplication::sendPostedEvents () at kernel/qcoreapplication.h:218
#24 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:210
#25 0x00000035d5a37abe in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#26 0x00000035d5a3b278 in ?? () from /lib64/libglib-2.0.so.0
#27 0x00000035d5a3b3a0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#28 0x00000034c3567936 in QEventDispatcherGlib::processEvents (this=0xb536a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#29 0x00000034c4821f8e in QGuiEventDispatcherGlib::processEvents (this=0x4fa9800, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x00000034c353ded2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 36}) at kernel/qeventloop.cpp:149
#31 0x00000034c353e2a4 in QEventLoop::exec (this=0x7fff63167a10, flags={i = 0}) at kernel/qeventloop.cpp:201
#32 0x00000034c3540439 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x0000000000406bff in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdevelop-3.9.94.20090827svn1016085/app/main.cpp:181

Reported using DrKonqi
Comment 1 Andreas Pakulat 2009-09-07 09:32:22 UTC
just comitted a fix for this in r1020715 (forgot to use the BUG keyword).
Comment 2 Dario Andres 2009-10-06 01:10:29 UTC
*** Bug 209536 has been marked as a duplicate of this bug. ***