Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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:20:47 -0400
From: "Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin1.dll problem with Hyperthreaded machines.
Message-ID: <20040830162046.GA919543@Worldnet>
References: <41316E85 DOT 8010707 AT melbourne DOT sgi DOT com> <OFDBD11567 DOT 72234441-ON85256F00 DOT 00560135-85256F00 DOT 00564CBC AT abinitio DOT com> <20040830155404 DOT GQ8900 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040830155404.GQ8900@trixie.casa.cgf.cx>
User-Agent: Mutt/1.4.1i

On Mon, Aug 30, 2004 at 11:54:04AM -0400, Christopher Faylor wrote:
> On Mon, Aug 30, 2004 at 11:42:51AM -0400, Chuck McDevitt wrote:
> >Here at the company I work for, we have one of our developers spending 
> >half his time trying to track down this problem, but so far with no luck.
> >He did find that forcing processor affinity helps avoid the problem, but 
> >that's not much of a solution.
> 
> No, but that's certainly in keeping with the tone of the problem.
> 
> >I keep trying to convince management to send a hyperthreaded machine that 
> >shows the problem to Christopher or Corinna, but they keep nixing the idea 
> >(I don't understand why).
> 
> I don't think either Corinna or I want another system, but if anyone is
> considering sending a hyperthreaded system, it should probably go to me
> and not Corinna since this is likely to be in code which I am
> responsible for.
> 
> Hmm.  Usually, in cases like this, by this time Pierre has stepped in
> and pointed in the general direction of where the problem lies.  I
> wonder if his recent patch to fork in cygwin-patches shows where at
> least one problem lies here.

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.

Pierre

--
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/