[PyKDE] Xft related crash

Stephan Jaensch sjaensch at gmx.net
Tue Dec 17 19:57:01 GMT 2002


Hi,

eric crashes when Xft is enabled for me via qtconfig (anti-aliasing does not 
have to be used). The QScintilla component seems to be the culprit, as it 
happens when I click on "New" or try to open an existing document. Here is 
the backtrace:

#0  0x407e668d in XGetFontProperty () from /usr/X11R6/lib/libX11.so.6
#1  0x403d349e in QFontPrivate::fillFontDef () from 
/opt/qt-copy/lib/libqt-mt.so.3
#2  0x403d9227 in QFontPrivate::initFontInfo ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#3  0x403dad65 in QFontPrivate::load () from /opt/qt-copy/lib/libqt-mt.so.3
#4  0x403d9cc9 in QFontPrivate::loadUnicode () from 
/opt/qt-copy/lib/libqt-mt.so.3
#5  0x403d9fd0 in QFontPrivate::load () from /opt/qt-copy/lib/libqt-mt.so.3
#6  0x403d1b0f in QFontMetrics::QFontMetrics ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#7  0x40411a2a in QPainter::fontMetrics () from /opt/qt-copy/lib/libqt-mt.so.3
#8  0x413b7257 in SurfaceImpl::Ascent () from 
/opt/qt-copy/lib/libqscintilla.so.0
#9  0x41404bd6 in Style::Realise () from /opt/qt-copy/lib/libqscintilla.so.0
#10 0x414064cd in ViewStyle::Refresh () from 
/opt/qt-copy/lib/libqscintilla.so.0
#11 0x413c404e in Editor::RefreshStyleData ()
   from /opt/qt-copy/lib/libqscintilla.so.0
#12 0x413ca5d1 in Editor::TextWidth () from 
/opt/qt-copy/lib/libqscintilla.so.0
#13 0x413d1e11 in Editor::WndProc () from /opt/qt-copy/lib/libqscintilla.so.0
#14 0x414043e1 in ScintillaBase::WndProc ()
   from /opt/qt-copy/lib/libqscintilla.so.0
#15 0x413b9385 in ScintillaQt::WndProc () from 
/opt/qt-copy/lib/libqscintilla.so.0
#16 0x413af60d in QextScintillaBase::SendScintilla ()
   from /opt/qt-copy/lib/libqscintilla.so.0
#17 0x413adebd in QextScintilla::setMarginWidth ()
   from /opt/qt-copy/lib/libqscintilla.so.0
#18 0x41371937 in sipDo_QextScintilla_setMarginWidth ()
   from /usr/lib/python2.2/site-packages/libqtextcmodule.so
#19 0x080c89d4 in PyCFunction_Call ()
#20 0x08076c43 in _PyExc_Fini ()
#21 0x08077c1d in PyEval_EvalCodeEx ()
#22 0x08079c98 in PyEval_EvalCode ()
#23 0x08076ce1 in _PyExc_Fini ()
#24 0x08077c1d in PyEval_EvalCodeEx ()
#25 0x080bcef9 in PyFunction_New ()
#26 0x080ab0c0 in PyObject_Call ()
#27 0x080b19ff in PyInstance_New ()
#28 0x080ab0c0 in PyObject_Call ()
#29 0x080783ff in PyEval_CallObjectWithKeywords ()
#30 0x080ae20e in PyInstance_New ()
#31 0x080ab0c0 in PyObject_Call ()
#32 0x08079d19 in PyEval_EvalCode ()
#33 0x08076cff in _PyExc_Fini ()
#34 0x08077c1d in PyEval_EvalCodeEx ()
#35 0x080bcef9 in PyFunction_New ()
#36 0x080ab0c0 in PyObject_Call ()
#37 0x080b19ff in PyInstance_New ()
#38 0x080ab0c0 in PyObject_Call ()
#39 0x080783ff in PyEval_CallObjectWithKeywords ()
#40 0x400168cb in sipEmitToSlot () from 
/usr/lib/python2.2/site-packages/libsip.so
#41 0x40ffda49 in sipProxyqt::proxySlot ()

I'm using current qt-copy from KDE cvs with SIP 3.5, PyQt 3.5, QScintilla 0.3 
and eric 3.0 (all self-compiled) on a Debian unstable system. Any hints? I 
tried on a stock SuSE 8.0 with Qt 3.0.3 and above SIP, PyQt, QScintilla and 
eric versions and it worked like a charm. Any hints as to what went wrong on 
the debian system? Any help is appreciated.

-- 
Ciao...




More information about the PyQt mailing list