Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Apr 2006 08:57:00 -0400 (EDT)
From:      Daniel Eischen <deischen@freebsd.org>
To:        Michael Vince <mv@thebeastie.org>
Cc:        Daniel Engberg <diizzyy@gmail.com>, freebsd-java@freebsd.org
Subject:   Re: Azureus 2.4.0.3 and Diablo JRE 1.5.0.06.00
Message-ID:  <Pine.GSO.4.64.0604120854390.19224@sea.ntplx.net>
In-Reply-To: <443C6A38.5090609@thebeastie.org>
References:  <ec96d1d50604102216h47dd84f3qf9c28097cc8843dd@mail.gmail.com> <443BAB15.6020802@thebeastie.org> <ec96d1d50604111732p2fbfc020ye7fd87cdea7a08cf@mail.gmail.com> <Pine.GSO.4.64.0604112235320.16944@sea.ntplx.net> <443C6A38.5090609@thebeastie.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Apr 2006, Michael Vince wrote:

> Daniel Eischen wrote:
>
>> No, it's not libpthread; it's a bug in the JVM.  See other emails
>> regarding this issue.  The work-around is to use -XX:+UseMembar
>> as an option to java.
>> 
> Will changing to libc_r threading library worked for him, how do you explain 
> that its not a threading issue if you can change the threading library and it 
> works.

Go see the archives.  libc_r is a user-space threads library and
isn't multi-CPU.  They are completely different libraries with
different run-time characteristics.  Libpthread and libthr are
likely to trigger other bugs that libc_r can't.

-- 
DE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0604120854390.19224>