> 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.
> > >
> > > 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
---------
Ernie Coskrey
SteelEye Technology, Inc.
--
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/
