Date: Wed, 10 Aug 2005 00:40:48 -0700 (PDT) From: Nick Johnson <freebsd@spatula.net> To: freebsd-java@freebsd.org Subject: Re: additional woes with 1.4.2-p7 on 5.4: Runtime.exec()? Message-ID: <20050810003632.F7871@turing.morons.org> In-Reply-To: <20050809165609.W7871@turing.morons.org> References: <20050809165609.W7871@turing.morons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Follow-up to this and the other pthread_test_cancel problem I posted
earlier...
Both problems are corrected by mapping libpthread to libc_r using
/etc/libmap.conf, so pretty sure it's a threading-related bug and probably
not specific to the JVM. (It seems like the JVM is great at tickling
subtle threading bugs.)
Of course the downside is that now I'm using libc_r when I'd rather be
using libpthread :-/
Nick
On Tue, 9 Aug 2005, Nick Johnson wrote:
> Ran into some more problems today. If I configure Resin to use jikes as its
> compiler, the first time it tries to compile something, the JVM goes
> unresponsive and begins consuming a large amount of CPU. truss -p shows the
> JVM in a tight kse_release loop.
--
"The aptly-named morons.org is an obscenity-laced screed..."
-- Robert P. Lockwood, Catholic League director of research
Nick Johnson, version 2.1 http://web.morons.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050810003632.F7871>