Now need to do a 1.5.10 release ASAP

Christopher Faylor
Fri Mar 26 16:10:00 GMT 2004

On Fri, Mar 26, 2004 at 10:55:27AM -0500, Christopher Faylor wrote:
>On Fri, Mar 26, 2004 at 04:38:27PM +0100, Corinna Vinschen wrote:
>>On Mar 26 00:32, Christopher Faylor wrote:
>>> On Thu, Mar 25, 2004 at 01:03:22PM -0500, Nicholas Wourms wrote:
>>> >cgf wrote:
>>> >>I have unearthed YA signal handling problem on Windows ME.  It's easy
>>> >>enough to duplicate but I can't figure out the reason for the behavior
>>> >>yet.  I've been hitting on it in my spare time but it is holding up the
>>> >>release.
>>> >
>>> >Can you be more specific?  I'm curious because I've been having
>>> >problems as well, but assumed they were related to local changes I
>>> >made.
>>> Surprisingly, it turned out to be a bash bug, AFAICT.  You should be able
>>> to trigger it on linux if you hold down ^C long enough.  Eventually, you'll
>>> get a signal handler calling kill, which calls the same signal handler, which
>>> calls kill, which calls the same signal handler, which calls kill, etc.
>>I just encountered the following problem:  When using the signal
>>patches from 2004-03-25, my bash scripts run, but never exit, unless
>>I press Ctrl-C.  When changing the script's first line to #!/bin/sh,
>>they exit fine.  Is that actually a bash bug?
>Do you have a shell script which demonstrates the problem?  I can't
>duplicate this.

Nevermind.  I duplicated the problem in the cygwin list by typing
"bash -l".  I was just typing "bash" and "rxvt -e bash" before.


More information about the Cygwin-developers mailing list