Unexpected HUP on Unix Domain Socket: Please help/explain about rct HOT 1 CLOSED

After some debugging, I figured out the problem (Thanks to gdb's non-stop mode which allowed me to debug the two threads better). To better illustrate what happens, I created a little diagram:

I fixed the test case by getting rid of the second thread and running the client connection code in a timer which is called from the event loop. This way, when the SocketClient is created, no epoll_wait() can wake up because no epoll_wait() is happening at this time.

For later, it might be a good idea to change SocketClient's startup code so that the socket fd is only added to the EventLoop after a connection is established.

from rct.