This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/18493] Infinite loop/deadlock? in __libc_recv (fd=fd at entry=300, buf=buf at entry=0x7f6042880600, n=n at entry=5, flags=-1, flags at entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
- From: "dan at censornet dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 05 Jun 2015 11:17:06 +0000
- Subject: [Bug libc/18493] Infinite loop/deadlock? in __libc_recv (fd=fd at entry=300, buf=buf at entry=0x7f6042880600, n=n at entry=5, flags=-1, flags at entry=258) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
- Auto-submitted: auto-generated
- References: <bug-18493-131 at http dot sourceware dot 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.