From owner-freebsd-java Wed Mar 7 16:23:11 2001 Delivered-To: freebsd-java@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id BC29437B718 for ; Wed, 7 Mar 2001 16:23:08 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA26665; Wed, 7 Mar 2001 19:22:35 -0500 (EST) Date: Wed, 7 Mar 2001 19:22:35 -0500 (EST) From: Daniel Eischen To: Bill Huey Cc: Greg Lewis , "Daniel M. Eischen" , java@FreeBSD.ORG Subject: Re: Java and libc/libpthread In-Reply-To: <20010307161130.A4910@gnuppy> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 7 Mar 2001, Bill Huey wrote: > > On Thu, Mar 08, 2001 at 01:55:58AM +1030, Greg Lewis wrote: > > 3. As I've been tinkering with the the 1.3 code I've so far been > > using the linuxthreads port to try and get native threads running > > as that means our code stays very very similar to the code for > > native threads under Linux. I haven't succeeded with this yet, > > but I don't believe thats because it can't work (its just lack of > > time to debug things so far). > > What ? Screw that. The LinuxThreads signal interaction with SIGCHLD, > etc... within an ill concieved thread/signal semantics specification > (aka Unix) is going to to be murder to deal with. > > I recommend doing it using the normal Solaris/Pthreads code instead. FWIW, I don't see our libpthread from deviating too much from the POSIX spec. I would like it to be as compliant as possible, including the way signals are handled in a multi-threaded environment. I know that Linux remaps SIGCHLD to SIGUSR[1 or 2?], and I hope that would not be necessary for FreeBSD. > I also might be able to get our pthread library to the general FreeBSD > community which might help with your port since we have it pretty well > debugged for our (this) purposes. I haven't seen the FreeBSD pthreads > userspace library so I can't comment on the benefits and draw backs of > doing this ? What is BSDIs threading model? You mentioned SIGALRM-based threads earlier and to me that meant it was similar to our current libc_r (which uses SIGPROF now). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message