This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: select() not interrupted by signals
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 11 Jan 2013 10:38:57 -0500
- Subject: Re: select() not interrupted by signals
- References: <50EFD041.4090108@towo.net>
- Reply-to: cygwin at cygwin dot com
On Fri, Jan 11, 2013 at 09:41:37AM +0100, 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.
"No interrupt"? I see a "HUP" but select() keeps going. That was the
way I designed it but apparently that differs from the way Linux works.
select() is not restartable like read() or write().
That behavior should be fixed in the next snapshot. If you are seeing
something different than this then that is not fixed.
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