Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: <6.0.1.1.0.20040406173921.037bd498@127.0.0.1>
To: Cygwin List <cygwin AT cygwin DOT com>
Cc: cygwin AT cygwin DOT com
Subject: Re: Cygwin1.dll problem with Hyperthreaded machines.
MIME-Version: 1.0
Message-ID: <OF9E11E2A7.5865292E-ON85256E6E.007AF5BE-85256E6E.007B5D18@abinitio.com>
From: Chuck McDevitt <cmcdevitt AT ABINITIO DOT COM>
Date: Tue, 6 Apr 2004 18:29:00 -0400
Content-Type: text/plain; charset="US-ASCII"
X-IsSubscribed: yes

I upgraded, and it didn't help.

under pdksh:

CMCDEVITT> test.ksh
Memory fault (core dumped)

CMCDEVITT> test.ksh
Test Failed......Path is empty

This is with Cygwin1.dll  1.5.9              (build time 2004-03-18 23:05) 
from www.cygwin.com/setup








Larry Hall <cygwin-lh AT cygwin DOT com>
04/06/2004 05:40 PM
Please respond to Cygwin List
 
        To:     Chuck McDevitt <cmcdevitt AT ABINITIO DOT COM>, cygwin AT cygwin DOT com
        cc: 
        Subject:        Re: Cygwin1.dll problem with Hyperthreaded 
machines.



At 05:17 PM 4/6/2004, you wrote:
>I've been running into a lot of problems with Cygwin on hyperthreaded 
>machines, when those machines are heavily loaded.
>
>For example, if I run this script:
>
>#! /bin/ksh
>mypath=$(pwd)
>while [[ ! -z $mypath ]]
>do
> mypath=$(pwd)
> if [[ -z $mypath ]]
> then
>  echo "Test Failed......Path is empty" 
> fi
>done
>
>in one shell, while running a large make in another, it will fail in a 
>variety of ways.
>Under pdksh, it sometimes exits the test because "mypath" is empty, or it 

>core dumps, or hangs, or gives error messages.
>Under bash, it hangs, crashes, or gives error messages (haven't seen it 
>exit the loop, but I didn't try long with bash).
>By "hang", I mean the shell stops using CPU time, and become 
>non-responsive, and can only be stopped by killing the process.
>The problem does not occur if hyperthreading is turned off.
>
>I've attached the output from cygcheck.
>
>
>Here are some example runs:
>
>#####Using pd KSH:
>
>CMCDEVITT> test.ksh
>Memory fault (core dumped)
>
>CMCDEVITT> test.ksh
>1861 [exiting thread] ksh 3260 cygthread::stub: erroneous thread 
>activation
>
>CMCDEVITT> test.ksh
>Memory fault (core dumped)
>
>CMCDEVITT> test.ksh
>Memory fault (core dumped)
>
>CMCDEVITT> test.ksh
>   2259 [exiting thread] ksh 2644 cygthread::stub: erroneous thread 
>activation
>
>#####Using BASH:
>
>CMCDEVITT> bash test.ksh
>3 [exiting thread] bash 3752 cygthread::stub: erroneous thread activation
>test.ksh: fork: Resource temporarily unavailable


Please update to Cygwin 1.5.9 and/or try a recent snapshot and report
back.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746 




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