[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE 3.5 BRANCH && gcc-4.1.0 && glibc-2.4 && linux-2.6.16
From:       Thiago Macieira <thiago () kde ! org>
Date:       2006-03-25 15:07:46
Message-ID: 200603251608.10513.thiago () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Pavel Troller wrote:
>  Just now, I'm guessing, whether the bug is in KDE (unprobable, it
> worked before the system upgrade), gcc/libstdc++, glibc/libpthread or
> kernel. It's the reason why I'm asking to see experience of others
> trying to do the same. Any help, what to try to debug this problem, is
> greatly appreciated!

Can you downgrade any of the variables and see if it helps?

The lock is happening due to g++'s thread-safe static variable 
initialisation (it requires a mutex).

Given your backtrace, I guess it is a glibc bug: it's deadlocking. 
libstdc++ tried to lock a mutex, that required a symbol lookup, which in 
turn required another mutex to be locked. But this is only a wild guess.
-- 
Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
  thiago.macieira (AT) trolltech.com     Trolltech AS
    GPG: 0x6EF45358                   |  Sandakerveien 116,
    E067 918B B660 DBD1 105C          |  NO-0402
    966C 33F5 F005 6EF4 5358          |  Oslo, Norway

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]