Reproducible crash in current kdevelop 3.4 from SVN

Jens Dagerbo jens.dagerbo at swipnet.se
Sun Oct 22 13:42:14 UTC 2006


On Sunday 22 October 2006 13:29, Matt Rogers wrote:
> On Sunday 22 October 2006 04:19, Andreas Pakulat wrote:
> > On 22.10.06 10:58:17, Michael Duelli wrote:
> > > > do you have a backtrace? (output of the backtrace tab in the KDE
> > > > crash dialog) --
> > >
> > > here is the correspondng backtrace:
> > >
> > > ------snip--------
> > > Using host libthread_db library
> > > "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled]
> > > [New Thread -1240504656 (LWP 14017)]
> > > [New Thread -1259418720 (LWP 14042)]
> > > [KCrash handler]
> > > #6  0xb67f88ed in QFont::QFont () from /usr/lib/qt3/lib/libqt-mt.so.3
> > > #7  0xb5e32579 in QXIMInputContext::setMicroFocus ()
> > >    from /usr/lib/qt3/plugins/inputmethods/libqxim.so
> > > #8  0xb5e5ee69 in QMultiInputContext::setMicroFocus ()
> > >    from /usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so
> >
> > Thats the "famous" XIM-Crash, if you can please update kdelibs to 3.5.5,
> > it contains fixes in konsolepart and katepart for this crash.
> >
> > Andreas
>
> I also thought we were working around this in KDevelop 3.4?

Imperfectly, but yes we do. But only for the crash in katepart, we can't do 
anything about the problems with konsolepart (afaik).

// jens




More information about the KDevelop-devel mailing list