[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:

[...]
> (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.

> BTW, using the libQtCore_debug.so.4 library didn't give me any useful
> line numbers or other debugging info.  If you load it into gdb and run
> 'info functions' all the symbols are defined as non-debugging symbols.
> This may have something to do with the way it was built.

That's bug #341807.

-- 
Captain Logic is not steering this tugboat.



Reply to: