Bug 197097 - kdevelop crashes on every startup
Summary: kdevelop crashes on every startup
Status: RESOLVED NOT A BUG
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 03:25 UTC by Stefan Böhmann
Modified: 2013-07-24 13:56 UTC (History)
5 users (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 Stefan Böhmann 2009-06-19 03:25:04 UTC
Application that crashed: kdevelop
Version of the application: 3.9.93 (using KDevPlatform 0.9.93)
KDE Version: 4.2.92 (KDE 4.2.92 (KDE 4.3 >= 20090617))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-gentoo-r1 x86_64

What I was doing when the application crashed:
Starting KDevelop (trunk/r983611) result immediately in a crash. 

------ < Console output > ------
<unknown program name>(23232)/ KDevelop::allocateRepository: picked duchain directory "/home/stefan/.kdevduchain/0"
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
QSqlDatabasePrivate::removeDatabase: connection 'GetNamespaceName-25708608-2' is still in use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'GetNamespaceName-25708608-4' is still in use, all queries will cease to work.
Calling appendChild() on a null node does nothing.
KCrash: Application 'kdevelop' crashing...
sock_file=/home/stefan/.kde4/socket-Pallas/kdeinit4__0

------ < / Console output > ------


 -- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
[Current thread is 0 (LWP 23232)]

Thread 2 (Thread 0x7fe1d92cb910 (LWP 23233)):
#0  0x00007fe1e591f4ed in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007fe1e5b8c6d7 in QWaitCondition::wait () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007fe1e2ae722e in KDevelop::DUChainPrivate::CleanupThread::run (this=0x1bb02a0) at /kdebuild/src/KDE/kdevplatform/language/duchain/duchain.cpp:280
#3  0x00007fe1e5b8b9b9 in QThreadPrivate::start () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007fe1e591b2d7 in start_thread () from /lib/libpthread.so.0
#5  0x00007fe1e41a138d in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe1e8dd2750 (LWP 23232)):
[KCrash Handler]
#5  0x00007fe1e4101645 in raise () from /lib/libc.so.6
#6  0x00007fe1e4102b63 in abort () from /lib/libc.so.6
#7  0x00007fe1e4143280 in malloc_printerr () from /lib/libc.so.6
#8  0x00007fe1e881c64e in KConfigPrivate::lookupData (this=0x19986a0, group=@0x19c98c8, key=<value optimized out>, flags=<value optimized out>) at /usr/include/qt4/QtCore/qbytearray.h:375
#9  0x00007fe1e8828333 in KConfigGroup::hasKey (this=0x7fff1835f8b0, key=0x7fe1e65272af "State") at /kdebuild/src/KDE/kdelibs/kdecore/config/kconfiggroup.cpp:1239
#10 0x00007fe1e6484dda in KMainWindow::applyMainWindowSettings (this=0x1a57c40, cg=@0x7fff1835f8b0, force=false) at /kdebuild/src/KDE/kdelibs/kdeui/widgets/kmainwindow.cpp:794
#11 0x00007fe1e64bfc15 in KXmlGuiWindow::applyMainWindowSettings (this=0x5ac0, config=@0x5ac0, force=6) at /kdebuild/src/KDE/kdelibs/kdeui/xmlgui/kxmlguiwindow.cpp:355
#12 0x00007fe1e64bf2e1 in KXmlGuiWindow::finalizeGUI (this=0x1a57c40) at /kdebuild/src/KDE/kdelibs/kdeui/xmlgui/kxmlguiwindow.cpp:348
#13 0x00007fe1e64cd2a5 in KXMLGUIFactory::addClient (this=0x1a7c930, client=0x1f34f40) at /kdebuild/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory.cpp:276
#14 0x00007fe1e82c81e8 in KDevelop::MainWindowPrivate::addPlugin (this=0x1a7cee0, plugin=0x1f34f30) at /kdebuild/src/KDE/kdevplatform/shell/mainwindow_p.cpp:89
#15 0x00007fe1e82c97a4 in KDevelop::MainWindowPrivate::qt_metacall (this=0x1a7cee0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1835fc70)
    at /kdebuild/build/KDE/kdevplatform/shell/mainwindow_p.moc:111
#16 0x00007fe1e5c70055 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007fe1e8573042 in KDevelop::IPluginController::pluginLoaded (this=0x5ac0, _t1=0x1f34f30) at /kdebuild/build/KDE/kdevplatform/interfaces/iplugincontroller.moc:92
#18 0x00007fe1e82cccd2 in KDevelop::PluginController::loadPluginInternal (this=0x1ba6c50, pluginId=@0x7fff18360710) at /kdebuild/src/KDE/kdevplatform/shell/plugincontroller.cpp:426
#19 0x00007fe1e82cf7a5 in KDevelop::PluginController::initialize (this=0x1ba6c50) at /kdebuild/src/KDE/kdevplatform/shell/plugincontroller.cpp:260
#20 0x00007fe1e82d3c37 in KDevelop::CorePrivate::initialize (this=0x1a008a0, mode=<value optimized out>) at /kdebuild/src/KDE/kdevplatform/shell/core.cpp:170
#21 0x0000000000407b30 in main (argc=1, argv=0x7fff18361b88) at /kdebuild/src/KDE/kdevelop/app/main.cpp:127

Reported using DrKonqi
Comment 1 Michael Pyne 2009-06-20 02:56:00 UTC
Stefan, have you recently updated glibc?

I run Gentoo as well and started getting crashes with malloc_printerr after upgrading glibc to 2.10.1.
Comment 2 Stefan Böhmann 2009-06-23 04:08:20 UTC
Yes. I've recently upgraded to glibc 2.10.1 too.
Comment 3 Michael Pyne 2009-06-23 05:36:24 UTC
Presumably yet more malloc checks were added in that version of glibc (and based on current gitweb, even more are to come in 2.11).

The console output would be more most interesting, you should be getting a  message about glibc detected a corruption or something like that.  Unfortunately I can't reproduce on call so I've not been able to get console output yet.
Comment 4 Stefan Böhmann 2009-06-23 14:27:54 UTC
Sorry - but I didn't get more console output than the few lines I already submitted above. 

If I can reproduce the crash (I was able to recently) how can I get more informations?
Comment 5 Michael Pyne 2009-06-23 23:07:37 UTC
Stefan, I think that unfortunately it would be required to re-emerge glibc with the debug USE flag set.
Comment 6 Stefan Böhmann 2009-06-25 12:51:26 UTC
Michael, I re-emerged glibc 2.10.1 with the USE flag 'debug' and with '-ggdb' in my CFLAGS. I could also reproduce the kdevelop crash and the backtrace contains some more information now. However - the console output did not change.


 -- Console:
stefan@Pallas ~ $ kdevelop                                                                                                    
WARNING: deleting stale lockfile /home/stefan/.kdevduchain/0/lock                                                             
<unknown program name>(6651)/ KDevelop::allocateRepository: picked duchain directory "/home/stefan/.kdevduchain/0"            
Calling appendChild() on a null node does nothing.                                                                            
Calling appendChild() on a null node does nothing.                                                                            
Calling appendChild() on a null node does nothing.                                                                            
Calling appendChild() on a null node does nothing.                                                                            
QSqlDatabasePrivate::removeDatabase: connection 'GetNamespaceName-37222464-2' is still in use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'GetNamespaceName-37222464-19' is still in use, all queries will cease to work.
Calling appendChild() on a null node does nothing.                                                                             
Calling appendChild() on a null node does nothing.                                                                             
KCrash: Application 'kdevelop' crashing...                                                                                     
sock_file=/home/stefan/.kde4/socket-Pallas/kdeinit4__0                                                                         

[1]+  Stopped                 kdevelop
stefan@Pallas ~ $



 -- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
[Current thread is 0 (LWP 6651)]

Thread 2 (Thread 0x7f2042e53910 (LWP 6652)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220
#1  0x00007f204f7636d7 in QWaitCondition::wait () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007f204c6bd6fe in KDevelop::DUChainPrivate::CleanupThread::run (this=0x26f8e40) at /kdebuild/src/KDE/kdevplatform/language/duchain/duchain.cpp:280
#3  0x00007f204f7629b9 in QThreadPrivate::start () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f204f4f22d7 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#5  0x00007f204dd7838d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f20529af750 (LWP 6651)):
[KCrash Handler]
#5  0x00007f204dcd8645 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007f204dcd9b63 in abort () at abort.c:88
#7  0x00007f204dd1a280 in malloc_printerr (action=2, str=0x7f204ddc6060 "free(): invalid pointer", ptr=0x19fb) at malloc.c:6201
#8  0x00007f204f7a046c in QString::free () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007f20500a112f in KXMLGUIFactoryPrivate::shortcutSchemeDoc (this=<value optimized out>, client=0x2f0e5f0) at /usr/include/qt4/QtCore/qstring.h:866
#10 0x00007f20500a26db in KXMLGUIFactoryPrivate::refreshActionProperties (this=0x25c23c0, client=0x2f0e5f0, doc={<QDomNode> = {impl = 0x7fffefcd8bb0}, <No data fields>})
    at /kdebuild/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory.cpp:326
#11 0x00007f20500a4439 in KXMLGUIFactory::addClient (this=0x25c2190, client=0x2f0e5f0) at /kdebuild/src/KDE/kdelibs/kdeui/xmlgui/kxmlguifactory.cpp:265
#12 0x00007f2051ea4228 in KDevelop::MainWindowPrivate::addPlugin (this=0x25c22a0, plugin=0x2f0e5e0) at /kdebuild/src/KDE/kdevplatform/shell/mainwindow_p.cpp:89
#13 0x00007f2051ea57e4 in KDevelop::MainWindowPrivate::qt_metacall (this=0x25c22a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffefcd8e90)
    at /kdebuild/build/KDE/kdevplatform/shell/mainwindow_p.moc:111
#14 0x00007f204f847055 in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007f2052150052 in KDevelop::IPluginController::pluginLoaded (this=0x19fb, _t1=0x2f0e5e0) at /kdebuild/build/KDE/kdevplatform/interfaces/iplugincontroller.moc:92
#16 0x00007f2051ea8d12 in KDevelop::PluginController::loadPluginInternal (this=0x26ebf70, pluginId=@0x7fffefcd9930) at /kdebuild/src/KDE/kdevplatform/shell/plugincontroller.cpp:426
#17 0x00007f2051eab7e5 in KDevelop::PluginController::initialize (this=0x26ebf70) at /kdebuild/src/KDE/kdevplatform/shell/plugincontroller.cpp:260
#18 0x00007f2051eafc77 in KDevelop::CorePrivate::initialize (this=0x25473c0, mode=<value optimized out>) at /kdebuild/src/KDE/kdevplatform/shell/core.cpp:170
#19 0x0000000000407b30 in main (argc=1, argv=0x7fffefcdada8) at /kdebuild/src/KDE/kdevelop/app/main.cpp:127
Comment 7 kdejkffdwitnas 2009-06-25 23:04:00 UTC
the same trouble: kdevelop crashes every single time at the very startup. here is my log. btw its different, mb my problem can be solved in another way?

plz help



quartz@ubuntu:~$ kdevelop
WARNING: deleting stale lockfile /home/quartz/.kdevduchain/0/lock
<unknown program name>(30014)/ KDevelop::allocateRepository: picked duchain directory "/home/quartz/.kdevduchain/0"                   
kdevelop(30014)/kdevplatform (shell) KDevelop::CorePrivate::initialize: Creating ui controller                                        
kdevelop(30014)/kdevplatform (sublime) Sublime::Area::Area: initial working-set: ""                                                   
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSet::connectArea: connecting "" to area Sublime::Area(0x89b9418, name = "code") 
kdevelop(30014)/kdevplatform (sublime) Sublime::Area::Area: initial working-set: ""                                                   
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSet::connectArea: connecting "" to area Sublime::Area(0x89b9a90, name = "debug")
kdevelop(30014)/kdevplatform (sublime) Sublime::Area::Area: initial working-set: ""                                                   
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSet::connectArea: connecting "" to area Sublime::Area(0x89ba5d8, name = "test") 
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget QObject(0x0)  QObject(0x0)  false                                                                
kdevelop(30014)/kdevplatform (shell) KDevelop::MainWindow::MainWindow: Bottom Left: 0                                                 
kdevelop(30014)/kdevplatform (shell) KDevelop::MainWindow::MainWindow: Bottom Right: 0                                                
kdevelop(30014)/kdevplatform (sublime) Sublime::AreaIndex::AreaIndex: copying area index                                              
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSet::connectArea: connecting "" to area Sublime::Area(0x89c6410, name = "code") 
kdevelop(30014)/kdevplatform (sublime) Sublime::AreaIndex::AreaIndex: copying area index                                              
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSet::connectArea: connecting "" to area Sublime::Area(0x89c7618, name = "debug")
kdevelop(30014)/kdevplatform (sublime) Sublime::AreaIndex::AreaIndex: copying area index                                              
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSet::connectArea: connecting "" to area Sublime::Area(0x89d34a8, name = "test") 
kdevelop(30014)/kdevplatform (sublime) Sublime::MainWindowPrivate::ViewCreator::operator: reconstructing views for area index 0x89c6fa0                                                                  
kdevelop(30014)/kdevplatform (sublime) Sublime::MainWindowPrivate::ViewCreator::operator: reconstructing root area                    
QObject::connect: Connecting from COMPAT signal (KTabBar::closeRequest(int))                                                          
kdevelop(30014)/kdevplatform (sublime) Sublime::MainWindowPrivate::reconstruct: RECONSTRUCT Sublime::Area(0x89c6410, name = "code")    ""                                                                
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89c6410, name = "code") QObject(0x0)  false                                      
kdevelop(30014)/kdevplatform (shell) KDevelop::MainWindow::loadSettings: Loading Settings                                             
kdevelop(30014)/kdevplatform (shell) KDevelop::MainWindow::loadSettings: Bottom Left: 0                                               
kdevelop(30014)/kdevplatform (shell) KDevelop::MainWindow::loadSettings: Bottom Right: 0                                              
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89c6410, name = "code") Sublime::Area(0x89c6410, name = "code") true             
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89c6410, name = "code") Sublime::Area(0x89c6410, name = "code") true             
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89c7618, name = "debug") Sublime::Area(0x89c7618, name = "debug") true
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89c7618, name = "debug") Sublime::Area(0x89c7618, name = "debug") true
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89d34a8, name = "test") Sublime::Area(0x89d34a8, name = "test") true
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89d34a8, name = "test") Sublime::Area(0x89d34a8, name = "test") true
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89c6410, name = "code") QObject(0x0)  true
kdevelop(30014)/kdevplatform (shell) KDevelop::WorkingSetWidget::workingSetsChanged: re-creating widget Sublime::Area(0x89c6410, name = "code") QObject(0x0)  true
kdevelop(30014)/kdevplatform (sublime) Sublime::MainWindow::loadSettings: loading settings for  "code"
kdevelop(30014)/kdevplatform (shell) KDevelop::CorePrivate::initialize: Creating plugin controller
kdevelop(30014)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from  "/var/tmp/kdecache-quartz/ksycoca4"
kdevelop(30014)/kutils (KSettings::Dispatcher) KSettings::Dispatcher::registerComponent: "kdevplatformproject"
ASSERT: "i < LastBreakpointKind" in file /home/quartz/kde/src/KDE/kdevplatform/debugger/breakpoint/breakpoint.cpp, line 58
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdevelop path = <unknown> pid = 30014
sock_file=/home/quartz/.kde4/socket-ubuntu/kdeinit4__0

[1]+  Stopped                 kdevelop
Comment 8 Michael Pyne 2009-06-26 05:01:33 UTC
Stefan, although you received no console output, your work in re-emerged was not wasted:

#7  0x00007f204dd1a280 in malloc_printerr (action=2, str=0x7f204ddc6060
"free(): invalid pointer", ptr=0x19fb) at malloc.c:6201

What malloc_printerr was supposed to print to console was that an invalid pointer was attempted to be free()'d.

The pointer being free()'d (assuming your QtCore headers are like mine) is:
inline QString::~QString() { if (!d->ref.deref()) free(d); } (which is the line number given for the KXMLGUIFactoryPrivate::shortcutSchemeDoc frame.  This line number was given because it was being run to run destructors prior to returning from that function when it crashed).

As it stands, I'm kind of stumped, there's no mis-use of QString in that function that I can tell.  Perhaps some subtle bug in Qt, previously masked over by coincidence?

It may be possible to use valgrind to see where that QString is mis-used but honestly I'm not sure why it would crash there.  Only other option I see is that the glibc check itself is wrong, but I'm not sure that's at all likely.
Comment 9 Michael Pyne 2009-06-28 03:38:15 UTC
Stefan, please see bug 196207 and bug 185225.  This crash isn't the same exact issue as noted in those two bugs I don't think, but apparently changing the values of the MALLOC_CHECK_ environment variable to 0 or 1 will ignore errors in buggy apps instead of crashing.  setting the value to 3 will give the current crash, and actually print out the error message instead of just crashing.
Comment 10 Andreas Pakulat 2009-06-29 22:53:52 UTC
*** Bug 196333 has been marked as a duplicate of this bug. ***
Comment 11 Christoph Feck 2009-07-22 16:24:32 UTC
This is probably the XMLGUI bug where it keeps references to deleted clients. Changing the malloc debugging options just ignores accesses to freed memory.
Comment 12 Michael Pyne 2009-07-23 03:30:33 UTC
Well if it's an XML-GUI bug it should show up in Valgrind I would think (I've not been able to reproduce memory corruption for the glibc/glib/KDE 4 bug I've been tracking in Valgrind, presumably because Valgrind doesn't detect heap corruption of valid memory when it's glibc corrupting its own heap :)

Also it's possible that you'll eventually get SIGSEGV instead of SIGABRT when running without MALLOC_CHECK_ (MALLOC_CHECK_ will crash with SIGABRT ASAP, otherwise the corruption won't be detected until later when the OS sends a SIGSEGV)
Comment 13 Dima Ryazanov 2010-04-17 01:59:53 UTC
I got a crash on startup, and tried running KDevelop in Valgrind... I got this - not sure if it's related:

==1573== Invalid read of size 2
==1573==    at 0x229A8F74: Konsole::TerminalDisplay::updateImage() (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x229ABB9D: Konsole::TerminalDisplay::qt_metacall(QMetaObject::Call, int, void**) (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x61FCC0E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293)
==1573==    by 0x22985575: ??? (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x61FCC0E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293)
==1573==    by 0x2295914D: Konsole::Emulation::showBulk() (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x22959362: Konsole::Emulation::qt_metacall(QMetaObject::Call, int, void**) (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x229C08AF: ??? (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x61FCC0E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293)
==1573==    by 0x61F9862: QObject::event(QEvent*) (qobject.cpp:1212)
==1573==    by 0x66BD12B: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:4300)
==1573==    by 0x66C371A: QApplication::notify(QObject*, QEvent*) (qapplication.cpp:4183)
==1573==  Address 0x31741660 is 0 bytes inside a block of size 960 free'd
==1573==    at 0x4C2471A: operator delete[](void*) (vg_replace_malloc.c:368)
==1573==    by 0x22985A3F: ??? (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x229AB6FC: Konsole::TerminalDisplay::processFilters() (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x22986A09: Konsole::Session::updateTerminalSize() (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x2298BB4F: Konsole::Session::qt_metacall(QMetaObject::Call, int, void**) (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x61FCC0E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293)
==1573==    by 0x229A3A5E: Konsole::TerminalDisplay::changedContentSizeSignal(int, int) (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x229A89F2: Konsole::TerminalDisplay::updateImageSize() (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x229A963D: Konsole::TerminalDisplay::updateImage() (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x229ABB9D: Konsole::TerminalDisplay::qt_metacall(QMetaObject::Call, int, void**) (in /usr/lib/libkonsoleprivate.so)
==1573==    by 0x61FCC0E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293)
==1573==    by 0x22985575: ??? (in /usr/lib/libkonsoleprivate.so)

(Since it mentions Konsole, I tried running Konsole in Valgrind, but did not see this problem, so I'm assuming it is in fact KDevelop's fault.)
Comment 14 Christoph Feck 2012-10-05 02:12:16 UTC
The cause for this crash could not be determined. If you still get this with a recent KDE version (4.8.5 or 4.9.x), please add an updated backtrace.
Comment 15 Christoph Feck 2013-07-24 13:56:15 UTC
No response, changing status. Please reopen, if you have more information.