Hello again, Apr 24, 2025, 19:05 by yelni...@tutamail.com:
> Hello Samuel, > > I haven't had much time to look into this in depth yet but I have adapted my > initial example s.t. it doesn't need an external program for the main socket > (please excuse my terrible C code and the formatting). > > The socket is first created nonblocking and once the first connection comes > in it is set to blocking and the connection is handled. As before the first > connection returns a nonblocking socket. > After spending a bit of time investigating I am a bit lost. I haven't found anything that is for me obviously wrong, but have not yet fully understood how things fit together. The only thing I have so far is that the flags of the wrong socket are the same as the original socket after the "select" as if something is not being updated correctly/in time. But why is always reproducible then? I am struggling to understand what could be different between the first and second "accept".
