Messages in this thread | | | Date | Mon, 13 Oct 2008 17:02:41 +0200 | From | Nicolas Cannasse <> | Subject | Re: recv() hangs until SIGCHLD ? |
| |
Nicolas Cannasse a écrit : >>> If there is data and the thread didn't wake up then that is a libc or >>> kernel problem; >>> but if there is no data, then look for cases where earlier >>> interrupted io actually >>> consumed the data already or blame the sending process not the receiver. >>> Also are the sockets blocking or non-blocking?
One other thing :
We tried to use a poll(POLLIN) on the socket before entering the recv(). The poll() does exit (and we are looping in case of EINTR result) but after that recv() blocks infinitely.
Hope that helps,
Nicolas
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |