[PyKDE] Segmentation fault with latest snapshot of sip & PyQt

[Phil Thompson]

On Sunday 01 June 2003 9:56 pm, Gordon Tyler wrote:
> On June 1, 2003 04:35 pm, Phil Thompson wrote:
> > It works fine for me. What version did it last work for you? A gdb
> > backtrace would be useful.
>
> I was previously using sip 3.6 and PyQt 3.6.

Not much has changed since 3.6 - nothing that I can think of that might make a 
difference with this.

> Here's the gdb backtrace for examples3/addressbook.py:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 5568)]
> 0x400f9a93 in __dynamic_cast () from /usr/lib/libstdc++.so.5
> (gdb) bt
> #0  0x400f9a93 in __dynamic_cast () from /usr/lib/libstdc++.so.5
> #1  0x414b561f in HighColorStyle::eventFilter ()
>    from /usr/lib/kde3/plugins/styles/highcolor.so
> #2  0x4048cb10 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
> #3  0x4048c9f1 in QObject::event () from /usr/lib/libqt-mt.so.3
> #4  0x404b9375 in QWidget::event () from /usr/lib/libqt-mt.so.3
> #5  0x411b3341 in sipQPushButton::event (this=0x82c8a90, a0=0x82c9758)
>     at sipqtQRadioButton.cpp:3382
> #6  0x4043c4da in QApplication::internalNotify () from
> /usr/lib/libqt-mt.so.3 #7  0x4043c2e4 in QApplication::notify () from
> /usr/lib/libqt-mt.so.3 #8  0x413fabb4 in sipQApplication::notify
> (this=0x824a5f8, a0=0x82c8a90, a1=0x82c9758) at sipqtQApplication.cpp:221
> #9  0x4043d1bd in QApplication::sendPostedEvents () from
> /usr/lib/libqt-mt.so.3
> #10 0x404b8e1f in QWidget::polish () from /usr/lib/libqt-mt.so.3
> #11 0x411b46ee in sipQPushButton::polish (this=0x82c8a90)
>     at sipqtQRadioButton.cpp:3709
> #12 0x4055b52b in QPushButton::sizeHint () from /usr/lib/libqt-mt.so.3
> #13 0x411b9f7e in sipDo_QPushButton_sizeHint (sipThisObj=0x82cfbb0,
>     sipArgs=0x810c0cc) at sipqtQPushButton.cpp:2818
> #14 0x080d465a in PyCFunction_Call ()
> #15 0x080761be in Py_MakePendingCalls ()
> #16 0x08076ba7 in PyEval_EvalCodeEx ()
> #17 0x080779eb in PyEval_CallObjectWithKeywords ()
> #18 0x08076119 in Py_MakePendingCalls ()
> #19 0x08076ba7 in PyEval_EvalCodeEx ()
> #20 0x080c8829 in PyStaticMethod_New ()
> #21 0x080b664c in PyObject_Call ()
> #22 0x080bd2c0 in PyMethod_Fini ()
> #23 0x080b664c in PyObject_Call ()
> #24 0x08077813 in PyEval_CallObjectWithKeywords ()
> #25 0x080b808a in PyInstance_New ()
> #26 0x080b664c in PyObject_Call ()
> #27 0x08077a87 in PyEval_CallObjectWithKeywords ()
> #28 0x080760a0 in Py_MakePendingCalls ()
> #29 0x08076ba7 in PyEval_EvalCodeEx ()
> #30 0x080779eb in PyEval_CallObjectWithKeywords ()
> #31 0x08076119 in Py_MakePendingCalls ()
> #32 0x08076ba7 in PyEval_EvalCodeEx ()
> #33 0x080c8829 in PyStaticMethod_New ()
> #34 0x080b664c in PyObject_Call ()
> #35 0x080bd2c0 in PyMethod_Fini ()
> #36 0x080b664c in PyObject_Call ()
> #37 0x08077813 in PyEval_CallObjectWithKeywords ()
> #38 0x080b808a in PyInstance_New ()
> #39 0x080b664c in PyObject_Call ()
> #40 0x08077a87 in PyEval_CallObjectWithKeywords ()
> #41 0x080760a0 in Py_MakePendingCalls ()
> #42 0x08076ba7 in PyEval_EvalCodeEx ()
> #43 0x08078e06 in PyEval_EvalCode ()
> #44 0x0809c0ad in PyRun_FileExFlags ()
> #45 0x0809b993 in PyRun_SimpleFileExFlags ()
> #46 0x080532be in Py_Main ()
> #47 0x08052e7f in main ()
> #48 0x4015ea51 in __libc_start_main () from /lib/libc.so.6
>
> Seeing as how the KDE HighColor style plugin was the last library involved,
> I just tried changing the Qt style from HighColor to Windows using qtconfig
> and now addressbook.py runs without crashing. Keramik also works, but B3
> and Default don't, probably because they're based on the HighColor plugin
> and Keramik is not.

All styles work for me - I'm using KDE 3.1.1 built from source tarballs. I'm 
not saying there isn't a bug - but I can't reproduce it.

Phil