Hi, here trying to figure out a SIGSEGV. Imagine we are sending TCP data to a remote peer. And while doing it, we call uv_close(), or we call uv_shutdown() (that will call uv_close() in its uv_shutdown_cb).
If there was pending TCP data being sent, could it happen that uv_write_cb is called with status error **after** having called uv_close() or uv_shutdown()? (If so, that would explain my problem). Now that I think about it, it makes sense since otherwise the app would not have a chance to clean the write buffer and so on. So, another (related) question: 1) After calling uv_close() (and before uv_close_cb is called) is there any API to check if the handle is (or is being) closed? (I think there is). 2) After calling uv_shutdown() (and before uv_shutdown_cb is called) is there any API to check if the handle is being shutdown? -- Iñaki Baz Castillo <[email protected]> -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
