This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: sigwait() and "sticky" signals (SIGWINCH...) in Cygwin 1.7
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 26 Aug 2009 16:55:31 -0400
- Subject: Re: sigwait() and "sticky" signals (SIGWINCH...) in Cygwin 1.7
- References: <loom.20090826T214123-598@post.gmane.org>
- Reply-to: cygwin at cygwin dot 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