X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 22 Mar 2010 12:03:52 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: recvfrom + MSG_PEEK = broken? Message-ID: <20100322110352.GA32321@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4BA7085D.3050307@cwilson.fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BA7085D.3050307@cwilson.fastmail.fm> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 22 02:04, Charles Wilson wrote: > I've been tracking down a problem in xinetd. It appears to be an issue > with using MSG_PEEK in recvfrom() on UDP sockets. Yes, that's a bug in Cygwin. The socket event handling got messed up when MSG_PEEK was used. I fixed that in CVS so it will be in 1.7.2. The last time I had problems with MSG_PEEK was back in 2006. Curious how seldomly it's used, apparently. Thanks for the simple testcase! It was very helpful to track down the problem easily. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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