[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#342658: libqt4-core: Locking Issue?



Ian Wienand <ianw@gelato.unsw.edu.au> writes:

> On Mon, Dec 12, 2005 at 01:39:13PM +0200, Brian Nelson wrote:
>> Ian Wienand <ianw@gelato.unsw.edu.au> writes:
>> 
>> [...]
>> > (gdb) back
>> > #0  0x2000000001363d81 in __pthread_sigsuspend (set=0x60000fffffbf7270)
>> >     at ../linuxthreads/sysdeps/unix/sysv/linux/ia64/pt-sigsuspend.c:32
>> > #1  0x2000000001362380 in __pthread_wait_for_restart_signal (self=0x200000000137edc8) at pthread.c:1216
>> > #2  0x200000000135d050 in __pthread_cond_wait (cond=0x6000000000004338, mutex=0x60000000000042e0) at restart.h:34
>> > #3  0x200000000103f400 in QReadWriteLock::lockForWrite () from /usr/lib/libQtCore.so.4
>> > #4  0x20000000011d0340 in qt_addObject () from /usr/lib/libQtCore.so.4
>> > #5  0x20000000011d0e50 in QObject::QObject () from /usr/lib/libQtCore.so.4
>> > #6  0x2000000001184e20 in QFactoryLoader::QFactoryLoader () from /usr/lib/libQtCore.so.4
>> > #7  0x200000000120b670 in QTextDecoder::~QTextDecoder () from /usr/lib/libQtCore.so.4
>> > #8  0x2000000001210ef0 in QTextCodec::codecForName () from /usr/lib/libQtCore.so.4
>> > #9  0x200000000120c160 in QTextEncoder::fromUnicode () from /usr/lib/libQtCore.so.4
>> > #10 0x200000000120efd0 in QTextCodec::codecForLocale () from /usr/lib/libQtCore.so.4
>> > #11 0x20000000010b30d0 in QString::toLocal8Bit () from /usr/lib/libQtCore.so.4
>> > #12 0x20000000010e04b0 in locale_encode () from /usr/lib/libQtCore.so.4
>> > #13 0x20000000010e06f0 in QFile::encodeName () from /usr/lib/libQtCore.so.4
>> > #14 0x20000000010f8e20 in QFileEngineHandler::QFileEngineHandler () from /usr/lib/libQtCore.so.4
>> > #15 0x20000000010e5460 in QFile::open () from /usr/lib/libQtCore.so.4
>> > #16 0x4000000000001070 in main ()
>> >
>> > It seems that lock in qt_addObject has already been taken by
>> > something.  Has anything changed in this area recently?
>> 
>> In the code?  No, not by me.  I don't see any reason why that lock would
>> be taken indefinitely anyway.
>
> I ruled out a few things, namely it seems to happen with both
> LinuxThreads and NPTL, so it seems unlikely that the threading
> library/kernel is at fault.
>
> The changes-4.0.1 file says that support has been added for SGI Altix,
> which means someone must have been interested in getting it working on
> IA64?  Any idea who that person might be?

No, no idea.

Does this still happen with Qt 4.1.0?

-- 
Captain Logic is not steering this tugboat.



Reply to: