X-Spam-Check-By: sourceware.org
Date: Mon, 6 Aug 2007 17:58:30 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Ernie Coskrey <Ernie DOT Coskrey AT steeleye DOT com>
cc: cygwin AT cygwin DOT com
Subject: RE: cygwin 1.5.20-1, spinning pdksh, 100% CPU
In-Reply-To: <76087731258D2545B1016BB958F00ADA123876@STEELPO.steeleye.com>
Message-ID: <Pine.GSO.4.63.0708061739230.5351@access1.cims.nyu.edu>
References: <76087731258D2545B1016BB958F00ADA123876 AT STEELPO DOT steeleye DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

FYI, there is no need to Cc: me -- I read the list.  I set my Reply-To:
for a reason -- please make sure your mailer respects it.

On Mon, 6 Aug 2007, Ernie Coskrey wrote:

> > Quite possibly.  There were changes to signal handling since 1.5.20,
> > IIRC. Unless I'm mistaken, there's even a patch for a race condition
> > in process handling code (though it's not in 1.5.24, I think).
>
> I just want to make sure I understand this - are you talking about a
> change that has been made since 1.5.24-2 was released, which is in the
> snapshot view now?  Or did you mean a fix that was made sometime between
> 1.5.20-1 and 1.5.24-2.

I meant the former, but I don't know if these changes have actually fixed
your problem.

> > > > Any suggestions would be appreciated!
> > >
> > > Posting a sequence of steps that reliably reproduces the problem for
> > > you would be great (but not necessarily easy).
>
> We've seen the issue happen with the following scripts.  Run a few
> instances of "tst.sh".  Occasionally, one will become hung - if you
> terminate the other tst.sh with Ctrl-C, you'll see that there's a
> subtest.sh shell that is using up all the CPU.
>
> First - generate "tstfile" by running
> ls -l /bin > tstfile
>
> tst.sh
> ======
> while true
> do
>         for ltr in a b c d e f g
>         do
>                 out=`./subtest.sh $ltr`
>                 echo Found $out
>                 date
>         done
> done
>
> subtest.sh
> ==========
> for i in `seq 1 100`
> do
>         f=`awk '{if(NR == i)print}' i=$i tstfile`
>         m=`/bin/echo $f | grep $1`
>         if [ ! -z "$m" ]
>         then
>                 echo $i: $m
>         fi
> done

I can't seem to reproduce this on my Core Duo Thinkpad with 2G RAM and
WinXP Pro after 20 minutes or so.

Any particulars about the machines on which this happens?  Are they
multi-core?  I don't recall seeing a cygcheck output from an affected
machine...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Belief can be manipulated.  Only knowledge is dangerous.  -- Frank Herbert

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