[PyKDE] Segmentation fault when running PyQt app

Gordon Tyler gordon at doxxx.net
Sun Apr 6 20:06:00 BST 2003


Hi all,

I seem to have somehow broken my PyQt snapshot. I'm using 
sip-x11-gpl-snapshot-20030322, PyQt-x11-gpl-snapshot-20030321, Python 2.2.2, 
and official KDE 3.1.1 and Qt 3.1.2-0woody1 Debian packages.

No matter how I recompile it, when I run a PyQt application, like the 
bigtable.py example from the example3 subdirectory, I get a segmentation 
fault.

This is the backtrace when run under gdb:

#0  0x400f6aeb in __dynamic_cast () from /usr/lib/libstdc++.so.5
#1  0x413a1d59 in HighColorStyle::drawPrimitive () from 
/usr/lib/kde3/plugins/styles/highcolor.so
#2  0x40517a4c in QHeader::paintSection () from /usr/lib/libqt-mt.so.3
#3  0x406323b6 in QTableHeader::paintSection () from /usr/lib/libqt-mt.so.3
#4  0x4063222f in QTableHeader::paintEvent () from /usr/lib/libqt-mt.so.3
#5  0x404b8763 in QWidget::event () from /usr/lib/libqt-mt.so.3
#6  0x4043b4da in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#7  0x4043b2e4 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#8  0x412ba187 in sipQApplication::notify () from 
/usr/local/lib/python2.2/site-packages/libqtcmodule.so
#9  0x403f1e83 in QETWidget::translatePaintEvent () from 
/usr/lib/libqt-mt.so.3
#10 0x403ee23d in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#11 0x403ff83d in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#12 0x4044cdae in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#13 0x4044cd0b in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#14 0x4043b632 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#15 0x412bbfc1 in sipDo_QApplication_exec_loop () from 
/usr/local/lib/python2.2/site-packages/libqtcmodule.so
#16 0x080d3fca in PyCFunction_Call ()
#17 0x08075fc4 in Py_MakePendingCalls ()
#18 0x080769b3 in PyEval_EvalCodeEx ()
#19 0x08078c06 in PyEval_EvalCode ()
#20 0x0809bc71 in PyRun_FileExFlags ()
#21 0x0809b557 in PyRun_SimpleFileExFlags ()
#22 0x080532bc in Py_Main ()
#23 0x08052e7f in main ()
#24 0x4015ca51 in __libc_start_main () from /lib/libc.so.6

I noticed that it's calling into libstdc++.so.5 which is what python2.2 is 
linked to, but the Qt and KDE libraries are linked to 
libstdc++-libc6.2-2.so.3. Would that mismatch be causing this problem?

Thanks,
Gordon




More information about the PyQt mailing list