From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: Re: New snapshot
27 Nov 1998 16:35:26 -0800
Message-ID: <19981127190619.A6332.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

On Sat, Nov 28, 1998 at 12:59:06AM +0100, Corinna Vinschen wrote:
>Christopher Faylor wrote:
>> 
>> On Fri, Nov 27, 1998 at 10:05:28AM -0800, Earnie Boyd wrote:
>> >> Ok.  I've tweaked a couple of things in the signal code.  There is a
>> >> new snapshot and a new binary at:
>> >>
>> >> ftp://cambridge.cygnus.com/pub/cygwin/
>> >> --
>> >> cgf AT cygnus DOT com
>> >> http://www.cygnus.com/
>> >>
>> >
>> >With this snapshot in NT 3.51 I occasionally get a pause after which
>> >the message "proc_terminate: WFSO(hwait_subproc) timed out" is
>> >displayed.  This happens with a repetitive null command (hold the
>> >ENTER button down).  Most often the repetitive ENTER will "freeze" the
>> >window and will not break so I must kill the process.
>> 
>> If you can duplicate this with an strace log it should be easy to track
>> down.
>> 
>> >I rebuilt the snapshot with no optimization switch.  I still get the
>> >afore mentioned error but haven't been able to get it to "freeze".
>> 
>> There is no evidence that optimization has anything to do with this,
>> AFAIK.
>> 
>> cgf
>
>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.
>
>I have attached an STRACE=0xfff output of a command `/usr/bin/echo', started
>from pdksh, which leads to a frozen shell.

I'll check this.  For future reference, you just need to set STRACE=1 to get
most of the interesting output.

-- 
cgf AT cygnus DOT com
http://www.cygnus.com/