Re: pthread weirdness
Dear debian-glibc. David asked me to respond to the list. I have brought
this issue up before and just wanted to ensure it's the same problem.
I'm running libc6
2.3.2.ds1-22
out of unstable at the moment, and it still exhibits the problem.
I had to give up on making debian work with this particular application
because I didn't want to maintain a seperate libc6 package and the
headaches that go with that.
The core issue as I remember it was that the NPTL in 2.3.2 libc6 was
borken version 0.70. We had to switch distributions that had 2.3.4 or
2.3.5 libc6 instead of 2.3.2.
>From the old bugs about it there were patches, and I'm guessing it's
possible upgrade just the underlying nptl code of libc.
It's this bug, but there may be others.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=108631
Perhaps once a 2.3.5 libc6 moves into unstable Debian can be used again.
-Joerg
On Wed, 15 Jun 2005, David Welton wrote:
> You should reply to the mailing list, and CC me, so that they can see
> there is a problem. Feel free to quote this message there.
>
> On 6/15/05, Joerg <joerg@archive.org> wrote:
>
> > We were seeing this in java as well. Is it possible that you are using
> > NPTL with the old Sarge glibc? We had an issue where we needed the
> > performance of NPTL but Debian didn't have a current glibc, so we tried
> > the app out on Fedora with glibc 2.3.5 and everything worked.
>
> "Old sarge glibc"? I'm just using regular old libc from sarge, which
> was just released. As far as NPTL, it wasn't a conscious choice, it's
> the default setup, as far as I can tell.
>
> > We will try to move back to Debian once a new glibc from experimental
> > moves back into unstable.
> >
> > Let me know what you find out/hear back on this if you want.
>
> It looks like this:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=108631
>
> Doesn't it...?
>
>
Reply to: