From owner-freebsd-current Fri May 4 19: 7:28 2001 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 44D4737B43F for ; Fri, 4 May 2001 19:07:24 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA04139; Fri, 4 May 2001 22:07:23 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f4526rZ67587; Fri, 4 May 2001 22:06:53 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15091.24637.184377.619873@grasshopper.cs.duke.edu> Date: Fri, 4 May 2001 22:06:53 -0400 (EDT) To: Daniel Eischen Cc: current@FreeBSD.ORG Subject: Re: Rfork'd threads, signals, and LDTs In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen writes: > > OK, thanks. Here's my guess at what should be changed for the Linux > emulator. If this looks correct, I'll commit it. > > Hmm, I wonder how linuxthreads works under FreeBSD without this > change... > Well, they've never worked perfectly, by any means. Perhaps this will improve the stability problems people have been reporting with the various linux jdks under FreeBSD/i386. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message