Bug#342658: libqt4-core: Locking Issue?

2005-12-13 Thread Ian Wienand
On Mon, Dec 12, 2005 at 01:39:13PM +0200, Brian Nelson wrote:
> Ian Wienand <[EMAIL PROTECTED]> writes:
> 
> [...]
> > (gdb) back
> > #0  0x21363d81 in __pthread_sigsuspend (set=0x6fbf7270)
> > at ../linuxthreads/sysdeps/unix/sysv/linux/ia64/pt-sigsuspend.c:32
> > #1  0x21362380 in __pthread_wait_for_restart_signal 
> > (self=0x2137edc8) at pthread.c:1216
> > #2  0x2135d050 in __pthread_cond_wait (cond=0x60004338, 
> > mutex=0x600042e0) at restart.h:34
> > #3  0x2103f400 in QReadWriteLock::lockForWrite () from 
> > /usr/lib/libQtCore.so.4
> > #4  0x211d0340 in qt_addObject () from /usr/lib/libQtCore.so.4
> > #5  0x211d0e50 in QObject::QObject () from /usr/lib/libQtCore.so.4
> > #6  0x21184e20 in QFactoryLoader::QFactoryLoader () from 
> > /usr/lib/libQtCore.so.4
> > #7  0x2120b670 in QTextDecoder::~QTextDecoder () from 
> > /usr/lib/libQtCore.so.4
> > #8  0x21210ef0 in QTextCodec::codecForName () from 
> > /usr/lib/libQtCore.so.4
> > #9  0x2120c160 in QTextEncoder::fromUnicode () from 
> > /usr/lib/libQtCore.so.4
> > #10 0x2120efd0 in QTextCodec::codecForLocale () from 
> > /usr/lib/libQtCore.so.4
> > #11 0x210b30d0 in QString::toLocal8Bit () from 
> > /usr/lib/libQtCore.so.4
> > #12 0x210e04b0 in locale_encode () from /usr/lib/libQtCore.so.4
> > #13 0x210e06f0 in QFile::encodeName () from /usr/lib/libQtCore.so.4
> > #14 0x210f8e20 in QFileEngineHandler::QFileEngineHandler () from 
> > /usr/lib/libQtCore.so.4
> > #15 0x210e5460 in QFile::open () from /usr/lib/libQtCore.so.4
> > #16 0x40001070 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?

-i


signature.asc
Description: Digital signature


Bug#343127: qt-x11-free: Will need to be rebuilt for IA64 with updated binutils

2005-12-12 Thread Ian Wienand
Package: qt-x11-free
Severity: important

Hi,

As noted in

http://lists.debian.org/debian-ia64/2005/12/msg6.html

kdevelop3 crashes the linker when it builds.

It turns out this is due to the linker bug (actually a bug from 'strip
-g')

http://sourceware.org/bugzilla/show_bug.cgi?id=1991

and a fix to the linker has been applied in

http://sourceware.org/bugzilla/show_bug.cgi?id=2008

However, this patch will cause the the linker to bail out, rather than
crash, so the package still won't build.

A rebuild of these libraries will be required when an updated binutils
is available, I have asked the binutils people about this in #342777

-i



signature.asc
Description: Digital signature


Bug#342658: libqt4-core: Locking Issue?

2005-12-11 Thread Ian Wienand
Package: libqt4-core
Version: 4.0.1-5
Followup-For: Bug #342658

I built your program like this

$ qmake-qt4 -project test.cpp
$ qmake-qt4 qt.pro
$ make

It seems this is a locking issue, a backtrace of when it is hung is below

(gdb) back
#0  0x21363d81 in __pthread_sigsuspend (set=0x6fbf7270)
at ../linuxthreads/sysdeps/unix/sysv/linux/ia64/pt-sigsuspend.c:32
#1  0x21362380 in __pthread_wait_for_restart_signal 
(self=0x2137edc8) at pthread.c:1216
#2  0x2135d050 in __pthread_cond_wait (cond=0x60004338, 
mutex=0x600042e0) at restart.h:34
#3  0x2103f400 in QReadWriteLock::lockForWrite () from 
/usr/lib/libQtCore.so.4
#4  0x211d0340 in qt_addObject () from /usr/lib/libQtCore.so.4
#5  0x211d0e50 in QObject::QObject () from /usr/lib/libQtCore.so.4
#6  0x21184e20 in QFactoryLoader::QFactoryLoader () from 
/usr/lib/libQtCore.so.4
#7  0x2120b670 in QTextDecoder::~QTextDecoder () from 
/usr/lib/libQtCore.so.4
#8  0x21210ef0 in QTextCodec::codecForName () from 
/usr/lib/libQtCore.so.4
#9  0x2120c160 in QTextEncoder::fromUnicode () from 
/usr/lib/libQtCore.so.4
#10 0x2120efd0 in QTextCodec::codecForLocale () from 
/usr/lib/libQtCore.so.4
#11 0x210b30d0 in QString::toLocal8Bit () from /usr/lib/libQtCore.so.4
#12 0x210e04b0 in locale_encode () from /usr/lib/libQtCore.so.4
#13 0x210e06f0 in QFile::encodeName () from /usr/lib/libQtCore.so.4
#14 0x210f8e20 in QFileEngineHandler::QFileEngineHandler () from 
/usr/lib/libQtCore.so.4
#15 0x210e5460 in QFile::open () from /usr/lib/libQtCore.so.4
#16 0x40001070 in main ()

It seems that lock in qt_addObject has already been taken by
something.  Has anything changed in this area recently?

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.

-i

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: ia64
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-rc4-gbb7e257e
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages libqt4-core depends on:
ii  libc6.1   2.3.5-7GNU C Library: Shared libraries an
ii  libfontconfig12.3.2-1.1  generic font configuration library
ii  libgcc1   1:4.0.2-5  GCC support library
ii  libstdc++64.0.2-5The GNU Standard C++ Library v3
ii  libunwind70.98.5-8   A library to determine the call-ch
ii  zlib1g1:1.2.3-6  compression library - runtime

libqt4-core recommends no packages.

-- no debconf information


signature.asc
Description: Digital signature