[PyKDE] PyQt-2.4 segfault in QString operator ==

John Galbraith john at bartok.lanl.gov
Fri Jul 27 18:46:38 BST 2001


I have PyQt-2.4, sip-2.4, Qt 2.3.0, and python 2.1 running on Redhat 7.1.
I get a segfault apparently on the QString handling.  So, I can't even run
the first tutorial example (tut1.py) because the button constructor takes a
string argument (for the label).

Here is the bottom of the call stack:

#0  0x407f2bd9 in operator== () from /usr/lib/qt-2.3.0/lib/libqt.so.2
#1  0x40909dc7 in QButton::setText () from /usr/lib/qt-2.3.0/lib/libqt.so.2
#2  0x4097c58d in QPushButton::QPushButton ()
   from /usr/lib/qt-2.3.0/lib/libqt.so.2
#3  0x40469828 in sipQPushButton::sipQPushButton (this=0x81911a0,
    a0=@0x818eeb8, a1=0x0, a2=0x0) at sipqtQPushButton.cpp:74
#4  0x404717ee in sipNew_QPushButton (sipSelf=0x818ee6c, sipArgs=0x8109854)
    at sipqtQPushButton.cpp:13135

and I believe the actual crash is on 

void QButton::setText( const QString &text )
{
    if ( btext == text )
	return;
...
}


I also cannot operate on the QString argument in sipNew_QPushButton (I
tried printing it out with it's latin1() method) without a segfault, so I
think that the problem may be sipConvertTo_QString() giving me a bad answer.

Thanks for any help,
       John
-- 
John Galbraith              	  email: jgalb at lanl.gov
Los Alamos National Laboratory,   home phone: (505) 662-3849
				  work phone: (505) 665-6301
				  home page: www.ece.arizona.edu:/~john




More information about the PyQt mailing list