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
In-Reply-To:	<41316E85.8010707@melbourne.sgi.com>
To:	chatz AT melbourne DOT sgi DOT com
Cc:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin1.dll problem with Hyperthreaded machines.
MIME-Version:	1.0
Message-ID:	<OFDBD11567.72234441-ON85256F00.00560135-85256F00.00564CBC@abinitio.com>
From:	Chuck McDevitt <cmcdevitt AT ABINITIO DOT COM>
Date:	Mon, 30 Aug 2004 11:42:51 -0400
X-IsSubscribed:	yes

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.

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).


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

- Raw text -