X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Mon, 22 Mar 2010 12:03:52 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: recvfrom + MSG_PEEK = broken?
Message-ID:	<20100322110352.GA32321@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4BA7085D DOT 3050307 AT cwilson DOT fastmail DOT fm>
MIME-Version:	1.0
In-Reply-To:	<4BA7085D.3050307@cwilson.fastmail.fm>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT 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

- Raw text -