X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAEd2GVCcKEdK/2dsb2JhbABFhXuyIHWBB4IgAQEBAwESERFKCwIBCA0NAhgOAgICHRMVEAEBBBsah2UGC59+iXuTMoEhkB8yYAONFolFhGmFEIUAgns
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date: Wed, 1 Aug 2012 14:35:54 -0400
Subject: RE: Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results
Message-ID: <A9D8BF3D8A74DF4A925FB541C0F39D2A16C25F155C@NIHMLBX15.nih.gov>
References: <A9D8BF3D8A74DF4A925FB541C0F39D2A16C25F128A AT NIHMLBX15 DOT nih DOT gov> <20120801090500 DOT GC18636 AT calimero DOT vinschen DOT de>
In-Reply-To: <20120801090500.GC18636@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id q71Ib6mB027553

> I applied a patch which should fix this problem.  It always uses
> WSARecvMsg now, if called from recvmsg, still provided it is possible,
> of course (No SOCK_STREAM, no AF_LOCAL).
> 
> I'm just generating a new developer snapshot.  Please give the today's
> snapshot from http://cygwin.com/snapshots/ a try.  Should be up in
> about
> half an hour.

The patched DLL now returns consistent msg_flags regardless of whether
or not the control message has been requested.  Thanks!

Could I ask for another favor that since the native WSA msg_flags get
propagated to the CYGWIN environment, the definitions for the additional
flag bits, MSG_MCAST and MSG_BCAST (as defined by WSA) to be added to
<cygwin/socket.h> please?

http://msdn.microsoft.com/en-us/library/windows/desktop/ms741645%28v=vs.85%29.aspx

Anton Lavrentiev
Contractor NIH/NLM/NCBI