Re: select() not interrupted by signals

2013-01-13 Thread Thomas Wolff
Am 12.01.2013 20:14, schrieb Christopher Faylor: On Sat, Jan 12, 2013 at 06:41:27PM +0100, Thomas Wolff wrote: Am 11.01.2013 16:38, schrieb Christopher Faylor: On Fri, Jan 11, 2013 at 09:41:37AM +0100, Thomas Wolff wrote: ... ... select() is not restartable like read() or write(). That behav

Re: select() not interrupted by signals

2013-01-12 Thread Christopher Faylor
On Sat, Jan 12, 2013 at 06:41:27PM +0100, Thomas Wolff wrote: >Am 11.01.2013 16:38, schrieb Christopher Faylor: >> 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.h

Re: select() not interrupted by signals

2013-01-12 Thread Thomas Wolff
Am 11.01.2013 16:38, schrieb Christopher Faylor: 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

Re: select() not interrupted by signals

2013-01-11 Thread Christopher Faylor
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). >

Re: select() not interrupted by signals

2013-01-11 Thread Corinna Vinschen
On Jan 11 13:55, Thomas Wolff wrote: > On 11.01.2013 09:52, Corinna Vinschen wrote: > >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 int

Re: select() not interrupted by signals

2013-01-11 Thread Thomas Wolff
On 11.01.2013 09:52, Corinna Vinschen wrote: 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 t

Re: select() not interrupted by signals

2013-01-11 Thread Corinna Vinschen
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 w

select() not interrupted by signals

2013-01-11 Thread Thomas Wolff
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 t