Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Tue, 25 Apr 2000 08:47:08 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: Possible race condition with sigsuspend in new net release
Message-ID: <20000425084708.C9750@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com
References: <46476C008A10D311BD0A0000C0775CF90151DF52@srv-exchange.adtran.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i
In-Reply-To: <46476C008A10D311BD0A0000C0775CF90151DF52@srv-exchange.adtran.com>; from tommy.reynolds@adtran.com on Tue, Apr 25, 2000 at 07:32:06AM -0500

On Tue, Apr 25, 2000 at 07:32:06AM -0500, TOMMY REYNOLDS wrote:
>I've been using the Z-Shell ZSH with Cygwin for quite a while, but it now
>hangs with the new Cygwin net release.  I managed to isolate the problem to
>the "sigsuspend()" call by extracting the sigsuspend test from the
>"./configure" script and trying to run the test code as a stand-alone
>program.  It hangs.  I then reran the test code under the "strace" program
>and the program exited normally.
>
>According to the CYGWIN mail archives, this problem has been around since at
>least 1997, but I didn't see any resolution to the problem.

Thanks for the detailed debugging information.  I will look into this.

I should point out that I use zsh *all* of the time on Cygwin.  It is essentially
my "test" system for new versions of the DLL since it uses so much of the UNIX
api -- especially with regard to signals.

I don't have any problems running zsh but there were some signal fixes that went
in after 1.1.0 was released.  Could you try a recent Cygwin snapshot and let
cygwin@sourceware.cygnus.com know if it works any better?

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com