Date: Tue, 11 Dec 2001 12:23:25 -0800 From: Joe Kelsey <joe@zircon.seattle.wa.us> To: freebsd-java@FreeBSD.ORG Subject: Re: jdk1.3.1p5 Message-ID: <15382.27453.18582.666321@zircon.zircon.seattle.wa.us> In-Reply-To: <15382.25997.525752.48613@caddis.yogotech.com> References: <20011210001702.10731.qmail@web14303.mail.yahoo.com> <20011210024138.GA3148@gnuppy> <20011209223635.A1152@absinthe> <15380.15272.167683.46148@caddis.yogotech.com> <20011210003200.C1152@absinthe> <15380.65513.794203.276229@caddis.yogotech.com> <20011211104902.GA8293@gnuppy> <15382.20613.76791.634824@caddis.yogotech.com> <15382.25038.873386.878424@zircon.zircon.seattle.wa.us> <15382.25997.525752.48613@caddis.yogotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Nate Williams writes: > I *really* beg to differ here. How much experience do you have with the > green threads code vs. native code? The green threads code is very > robust. The green threads code for *BSD is *very* broken. If I link the plugin java_vm with libc and tell it to use green threads, it *immediately* dies due to a null-pointer reference in green_sigprocmask, a *BSD-specific function. I can solve that problem, and then encounter a new crash due to another null-pointer reference in another section of *BSD-specific green threads code. From my perspective, these crashes have *nothing* to do with the plugin per se, but rather have a lot to do with broken green threads implementation. It is nice that your specific application does not tickle the many green threads bugs that I uncovered. It became too much work to unravel all of the broken stuff in green threads. You are welcome to try to do it yourself. /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15382.27453.18582.666321>