[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 - SOLVED
From:       Michael Pyne <michael.pyne () kdemail ! net>
Date:       2006-03-26 20:01:12
Message-ID: 200603261501.17294.michael.pyne () kdemail ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 26 March 2006 08:34, Pavel Troller wrote:
> I did. No success. Applied even gcc patches. No success. Then I've got SVN
> gcc and used its libstdc++.so.6 (and libgcc_s.so.1, because it's tied
> together) instead of 4.1.0 versions. IT WORKS! No more deadlocks. I've left
> rest of gcc suite from raw 4.1.0 and let's see, what'll show more.
>
> So, the problem is definitely in the libstdc++ from 4.1.0 and I'm really
> curious, why in gentoo environment it doesn't show up.

It may depend on the configure settings used to compile gcc.  Gentoo used to 
(or may still, but I think they changed this) use some faster memory 
allocator by default with libstdc++ (not a Gentoo patch, just a different 
configure selection) instead of the default slower memory allocator.

If the gcc devs had implemented it right that would have been fine but their 
memory allocator didn't work in the presence of visibility support.  I 
suspect something like that is going on here, you only trigger the bug in a 
combination of certain circumstances.

Regards,
 - Michael Pyne

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