Problem solved by this: https://groups.google.com/d/msg/libuv/onPZgBM9aIk/vzGlHD5v5aYJ
All I needed to do was ensure the streams were closed on the close_cb for the uv_process_t! On Wednesday, October 22, 2014 9:06:43 PM UTC-3, Thiago Arruda wrote: > > I have come across a tricky situation. > > After starting a process with stdin, stdout and stderr connected to the > parent, I send it some input and then close stdin to notify the child no > more data is coming. As expected, the child exits(the uv_process_t exit_cb > is called) but none of the read callbacks associated with the stdout/stderr > streams are called. Is this a bug or it's something can happen in some > scenarios? > > I had asked in another thread( > https://groups.google.com/forum/#!searchin/libuv/order/libuv/onPZgBM9aIk/OiFMXtRQoEEJ) > > if there was any guarantee that exit_cb was the last callback invoked, but > the answer was no. If what is happening is not a bug, then how can I know > when the process won't send any more data? > > Thanks in advance > -- 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 http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
