Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 13 Dec 2003 15:03:06 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: System calls getting interrupted with signals, even with SA_RESTART Message-ID: <20031213200305.GA17264@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <005601c3c1b3$21850ba0$ed01a8c0 AT jewel> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005601c3c1b3$21850ba0$ed01a8c0@jewel> User-Agent: Mutt/1.4.1i On Sat, Dec 13, 2003 at 02:55:52PM -0500, Robby Dermody wrote: >Hey guys, > >I've ran into a little problem. I have been porting an piece of software to >Cygwin. It builds and initially runs fine, but when I get a SIGALRM signal, >which I use for asynchronous timers, a few things return with an EINTR: > >-select() From the SUSv3 documentation on select(): If SA_RESTART has been set for the interrupting signal, it is implementation-defined whether the function restarts or returns with [EINTR]. select() does not currently honor SA_RESTART on cygwin. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/