Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Tue, 27 Aug 2002 14:03:32 +0200 From: Corinna Vinschen To: Cygwin Subject: Re: Help with unix sockets and poll Message-ID: <20020827140332.X5475@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: Cygwin References: <007001c24da6$858b3d40$0b01a8c0@Camelot> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <007001c24da6$858b3d40$0b01a8c0@Camelot> User-Agent: Mutt/1.3.22.1i On Tue, Aug 27, 2002 at 10:35:35AM +0200, Pierluigi 'Lanugo' Rolando wrote: > Hi, > I've tried to port some code that relies heavily on unix domain sockets for > IPC from Linux to Cygwin, and I've encountered some problems. It seems that > either unix domain sockets (created by socketpair() ) or the poll() library > call are broken. > I'm attaching the smallest test case I've been able to write that reproduces > the problem. Under linux (2.4.19/2.4.18 w/ glibc 2.2.4) the program > terminates correctly, while under cygwin it reports a POLLERR after the > first character is written on the socket. My cygwin DLL is version Thanks for the testcase! I'm just investigating that and it looks like an error in Cygwin. As a workaround, don't check for POLLERR in your application for now. It doesn't have a useful meaning, AFAICS. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/