Are you still accessing libuv (sans explicitly thread-safe functions such as uv_async_send) from multiple threads, as you mentioned earlier? If so, I'd suggest fixing that first. In conjunction, I recommend running TSan and making sure it runs cleanly before checking for library or logic problems. Then, if it is still a rare failure, I recommend debugging under `rr` as you'll be able to run forward to the problem, then walk backwards through the code to see what happened to your state and file descriptors.
On Sat, May 8, 2021 at 11:27 AM [email protected] < [email protected]> wrote: > Hi: > > Addition to my last message. When uv__nonblock() fails it is indicative > of a Linux FIONBIO ioctl() failure. What would cause > setting non-blocking mode to fail ? > > Best Regards, > > Paul R. > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/libuv/CADnnjUW6KL3OQw5C54aNfKh95z1OpQiq2bgVtXya8z_BeqMS9w%40mail.gmail.com.
