From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: Re: New snapshot
27 Nov 1998 19:35:32 -0800
Message-ID: <19981127220546.A10879.cygnus.cygwin32.developers@cygnus.com>
References: <19981127180528 DOT 20612 DOT rocketmail AT send105 DOT yahoomail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Corinna Vinschen <corinna DOT vinschen AT cityweb DOT de>,
        cygwin32-developers AT cygnus DOT com

Ok.  I think I've tracked down at least two more problems.  I wasn't
making sure that the signal was fully delivered before a sigsuspend
returned.  I don't know why I wasn't seeing problems with my shell,
zsh, which uses sigsuspend.  The first or second time I fixed this
problem I saw this behavior with zsh.

Hmm.  I think it's time to add a comment to the code.

I've updated the binary and the snapshot at:

ftp://cambridge.cygnus.com/pub/cygwin/

Please let me know what's wrong with *this* one.

-chris

On Sat, Nov 28, 1998 at 12:59:06AM +0100, Corinna Vinschen wrote:
>NT40SP3, CYGWIN="binmode ntea notty"
>
>bash:
>   works as before as expected.
>
>tcsh:
>   On command execution, sometimes approx. 10 seconds 'til prompt reappears
>   but mostly indeterminant freeze after command execution.
>
>pdksh:
>   On command execution, approx. 10 seconds 'til same message as
>   described in my previous mail:
>
>      ****** exceptions.cc:419 __get_signal_mutex failed, res 258, error 2
>        0) function exceptions.cc, line 365
>
>   Very frequent indeterminant freeze after the above message.