X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 26 Aug 2009 16:55:31 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: sigwait() and "sticky" signals (SIGWINCH...) in Cygwin 1.7 Message-ID: <20090826205531.GB13911@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Wed, Aug 26, 2009 at 08:13:37PM +0000, Waldemar Rachwal wrote: >I observe strange behavior of sigwait() with SIGWINCH signal (and possibly >others... like SIGCHLD). > >Look at a short program below. In a loop I wait for SIG{INT,WINCH} signals. >SIGWINCH, similarly to SIGCHLD is ignored by default, so I had to register a >dummy signal handler for it. > >When the program (compiled with gcc-4) is running, SIGWINCH is never returned by >the sigwait() immediately after window's resize, but always along with >successive SIGINT when I press Ctrl+C. If you are talking about the resizing of, say, the standard Windows console window that Cygwin runs in by default then that is, unfortunately, a limitation in Cygwin's implementation of SIGWINCH that is probably not going to change. It should work much better when running in rxvt, mintty, or xterm though. 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