public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dan at censornet dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18493] Infinite loop/deadlock? in __libc_recv (fd=fd@entry=300, buf=buf@entry=0x7f6042880600, n=n@entry=5, flags=-1, flags@entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
Date: Fri, 05 Jun 2015 11:17:00 -0000	[thread overview]
Message-ID: <bug-18493-131-TcIVd25zVA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18493-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18493

--- Comment #1 from Dan Searle <dan at censornet dot com> ---
Typo, original: "I've even tried adding a poll() call for POLLRDNORM on the
socket before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make
sure there's data available on the socket before calling poll(), but it makes
no difference."

Should have been: "I've even tried adding a poll() call for POLLRDNORM on the
socket before calling recv() with MSG_PEEK | MSG_WAITALL flags to try to make
sure there's data available on the socket before calling *recv()*, but it makes
no difference."

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-06-05 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 11:12 [Bug libc/18493] New: " dan at censornet dot com
2015-06-05 11:13 ` [Bug libc/18493] " dan at censornet dot com
2015-06-05 11:17 ` dan at censornet dot com [this message]
2015-06-05 11:44 ` schwab@linux-m68k.org
2015-06-05 11:52 ` dan at censornet dot com
2015-06-10 14:00 ` fweimer at redhat dot com
2015-06-11  8:00 ` dan at censornet dot com
2015-06-11  8:07 ` fweimer at redhat dot com
2015-06-11  8:08 ` fweimer at redhat dot com
2015-06-11  8:15 ` dan at censornet dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-18493-131-TcIVd25zVA@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).