rodda at kde.org
Wed Aug 30 02:37:21 UTC 2006
On Wednesday 30 August 2006 09:38, mwoehlke wrote:
> Every now and then, KDevelop (I'm running 3.3.91) crashes when loading a
> project. Normally, I wouldn't post this as it appears to have only
> partial debugging information, except that 'col=-1' at #14 looks
> suspicious. IIRC I have heard a lot of '-1' bugs on kate-devel, so I am
> not sure this is KDevelop's fault, although the call at #15
> (ProjectSession::loadDocument) looks like KDevelop. Any thoughts?
> (KATE folks, to whom I have cross-posted, does this look familiar?)
> I am currently running KDE 3.4.3 but was in the process of building
> 3.5.4; I am willing to flip on debugging for the whole enchilada if
> someone reminds me what the flag is. :-)
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread -1208109376 (LWP 25441)]
> [New Thread -1211667536 (LWP 9116)]
> [KCrash handler]
> #4 0x00bac696 in XTranslateCoordinates () from /usr/X11R6/lib/libX11.so.6
> #5 0x0729dc50 in QWidget::mapFromGlobal ()
> from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #6 0x00a05ace in QXIMInputContext::setMicroFocus ()
> from /usr/lib/qt-3.3/plugins/inputmethods/libqxim.so
This is a known bug in distro patched versions of Qt. Dirk Mueller was
working on it about a week ago, so it may already be fixed.
The solution I use locally is to delete libqxim.so
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the KDevelop-devel