I thought this article was going to be about the blocking recv() with a closed socket "issue" in linux, but it wasn't. For those that don't know, linux behaves

I thought this article was going to be about the blocking recv() with a closed socket "issue" in linux, but it wasn't. For those that don't know, linux behaves differently than other unix in that a thread blocked in recv() will remain blocked in recv if another thread closes the underlying socket. AKA, the article works because GDB is interrupting the recv() call (or the socket was marked nonblocking), not because simply closing a socket wakes up a blocked recv() in linux.