X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 11 Jan 2013 09:52:56 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: select() not interrupted by signals Message-ID: <20130111085256.GC17162@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <50EFD041.4090108@towo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <50EFD041.4090108@towo.net> User-Agent: Mutt/1.5.21 (2010-09-15) 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 Jan 11 09:41, Thomas Wolff wrote: > I had previously reported "select() hanging after terminal killed" > (http://cygwin.com/ml/cygwin/2011-05/msg00418.html). > It turns out that select() does not get interrupted by a SIGWINCH > signal either (with likely the same cause). > This raises problems with interactive programs that want to react to > window size changes (like text editors). > > See attached updated test case; run the program, while select() is > waiting (before 5 second timeout each), change window size and see > no interrupt. > On other systems, select() is interrupted (test case: from mintty, > remote login to SunOS; also showing the terminal is not involved in > the problem). > > This bug did not exist in cygwin 1.5; I see some Changelog entries > from 2011-12-13 or 2012-01-22 which might be related. Just for clarity, did you test with the latest snapshot? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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