This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Using recvmsg() with non-unicast datagram (UDP) socket: inconsistent results
- 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
- References: <A9D8BF3D8A74DF4A925FB541C0F39D2A16C25F128A@NIHMLBX15.nih.gov> <20120801090500.GC18636@calimero.vinschen.de>
> 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