Date: Mon, 04 Sep 2006 14:33:58 +1000 From: David Nugent <davidn@datalinktech.com.au> To: Yamada Ken Takeshi <ken@tydfam.jp> Cc: freebsd-java@freebsd.org Subject: Re: diablo-jdk1.5.0 core dumps w/ -current Message-ID: <44FBACB6.1030604@datalinktech.com.au> In-Reply-To: <20060901.230842.74753654.ken@tydfam.jp> References: <20060901.230842.74753654.ken@tydfam.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Yamada Ken Takeshi wrote: > Recent -current, ca. a week or so causes a crash like below. > Is it unique to me? or commonly noticed? > Noticed first a few weeks ago in -current. You would need to rebuild jdk against recent -current libc and threading libraries to return functionality due to -current's thread libraries (which have had no version bump yet) being dependent on functionality in -current's libc.7, but diablo loads libc.6. As a fast workaround if you just want to get diablo working again, you should be able to libmap.conf one of the other thread libs instead of libthr. I don't know how well it works, but others have reported success.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44FBACB6.1030604>