X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sat, 19 Sep 2009 10:53:36 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [1.7] sigwait bug (SIGCHLD delayed to a next regular signal) Message-ID: <20090919145336.GA1502@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20090918213522.GA12527@ednor.casa.cgf.cx> <20090919144319.GA31739@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090919144319.GA31739@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sat, Sep 19, 2009 at 10:43:19AM -0400, Christopher Faylor wrote: >I was explaining the problem to you. As I said, SIGCHLD is a signal >like any other signal and if you had tried to use a similar mechanism to >trap, say, SIGINT, you would have seen the same problem. ...and in fact, you did mask SIGINT in your example but, since you didn't set a handler for it, sigwait() did detect the signal. 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