Bug#752237: libc0.3: send() asked to transmit 0 chars still triggers recv() on Hurd

[Richard Braun <rbraun@sceen.net>]

On Sat, Jun 28, 2014 at 10:48:56AM +0200, Richard Braun wrote:
> On Sat, Jun 21, 2014 at 03:56:46PM +0200, Andreas Cadhalpun wrote:
> > This is because the client is calling:
> > 	send(sockfd, "", 0, 0)
> > 
> > Normally this doesn't trigger recv() in the server and thus can be
> > used to test, whether the socket is working.
> > But on Hurd it actually sends an empty message, so that the real
> > message, which is sent later, is not received.
> 
> Hello,
> 
> Thanks for the report. There are actually two sides of the problem.
> First, I agree that there seems to be a bug, but let's take a closer

I've committed a fix upstream [1], please see if it solves your issues
as well.

-- 
Richard Braun

[1] http://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=6f856c62613ffc82bf3572a372d2851638c2fb90