On September 16, 2005 19:27, Bob Tanner wrote: > Package: libqt3-mt > Version: 3:3.3.4-8 > Severity: important > > Recently upgrade from 3.3.3 to 3.3.4-8 and I have several application > that all segfault in the same class and method. > > [KCrash handler] > #3 0xb6c35f34 in QShared::deref (this=0x34343942) at qshared.h:50 > #4 0xb702fcc6 in QString::deref (this=0xbfffebec) at > tools/qstring.cpp:1549 #5 0xb702ff57 in QString::operator= > (this=0xbfffebec, s=@0xbfffebf4) at tools/qstring.cpp:1594 > > The partital application list: kmail, kontact, pwmanager, wlassistant, > showeq, kate. > > Using pwmanager (http://pwmanager.sourceforge.net) as an example. Same > tarball, linked libqt3c102-mt (3:3.3.4-3) is rock solid. Recompile > pwmanager and link against libqt-mt (3:3.3.4-8) consisten segfault in > QShared::deref (this=0x34343942) at qshared.h:50. Using the very latest Sid (i.e. Qt 3.3.5, etc.), does this problem still exist? If so, could you provide a list of steps to reproduce the problem? I.e. open application foo, click here, click there, segfault, etc. Your message didn't specify whether the segfaults occured on startup, in which case I can't reproduce it (kmail is solid here). And as Josh Metzler pointed out, please ensure that everything is being built with gcc-4.0. Thanks, Christopher Martin
Attachment:
pgpmxzcOhzyA0.pgp
Description: PGP signature