Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 30 Aug 2004 12:54:47 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin1.dll problem with Hyperthreaded machines. Message-ID: <20040830165447.GT8900@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <41316E85 DOT 8010707 AT melbourne DOT sgi DOT com> <20040830155404 DOT GQ8900 AT trixie DOT casa DOT cgf DOT cx> <20040830162046 DOT GA919543 AT Worldnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040830162046.GA919543@Worldnet> User-Agent: Mutt/1.4.1i On Mon, Aug 30, 2004 at 12:20:47PM -0400, Pierre A. Humblet wrote: >Huh? I don't even own a single dog, just a WinME. It has crossed my >mind that the fork bug has something to do with the hyperthreaded >machine problem, and even that it might well be the last bug in Cygwin. >Processor affinity not helping is consistent with the fork bug. Yup. That's what I was thinking. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/