From owner-freebsd-java Tue Dec 11 12:53:54 2001 Delivered-To: freebsd-java@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id E426737B41E for ; Tue, 11 Dec 2001 12:53:49 -0800 (PST) Received: from caddis.yogotech.com (yogotech.nokia.com [4.22.66.156]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA11375; Tue, 11 Dec 2001 13:53:47 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id fBBKrkw01608; Tue, 11 Dec 2001 13:53:46 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15382.29273.887179.205335@caddis.yogotech.com> Date: Tue, 11 Dec 2001 13:53:45 -0700 To: Joe Kelsey Cc: freebsd-java@FreeBSD.ORG Subject: Re: jdk1.3.1p5 In-Reply-To: <15382.27453.18582.666321@zircon.zircon.seattle.wa.us> 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> <15382.27453.18582.666321@zircon.zircon.seattle.wa.us> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > 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. Do I have to repeat myself here? Apparently so. As I stated before: > There are assumptions in the plugin code that no longer work due to > green threads, but that's because the plugin folks never tried to get > things working under green threads. The code works fine. It's like saying that libc is broken for multithreaded programs. It's not broken, it's just that the program that is using libc (vs. libc_r) is not designed correctly to work with libc. > 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. See above. The green threads code is quite robust actually. > It is nice that your specific application does not tickle the many green > threads bugs that I uncovered. *sigh* Trying to have a conversation with you is worthless, so I'll quit trying. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message