Date: Thu, 16 Aug 2012 14:43:48 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Another sigwaitinfo problem (with testcase)
Message-ID: <20120816184348.GA16945@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <502B3567 DOT 9090808 AT dancol DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <502B3567.9090808@dancol.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Aug 14, 2012 at 10:36:39PM -0700, Daniel Colascione wrote:
>When run on a Linux machine, this program starts up and blocks on sigwaitinfo.
>You can suspend and resume the program using usual job control facilities, and
>on SIGINT, the program prints a message and exits. When the program resumes
>after being stopped, it prints "resumed".
>
>With the 2012-08-07 Cygwin snapshot, this program prints "resumed" immediately
>after receiving SIGTSTP, then fails to respond to any signal, even signals not
>in the blocked set. A simpler test program that just calls "raise (SIGSTOP)"
>property stops itself before resuming execution.

This should be fixed in the latest snapshot.

Thanks for the test case.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple