Dear all, I am trying to wrap libuv as an extension package for an environment. It seems mostly straightforward, and I'll just run a libuv event loop in another thread, they can communicate via pipes.
However, there is a potential issue with signals. The host environment handles some signals, and AFAICT libuv does use a couple of signals for its own purposes. E.g. they can both start child processes, and they set a signal handler for SIGCHLD. Actually, AFAIR libuv sets up some signal handlers already when an event loop is created. I realize that this is not a very specific question, but how much does libuv rely on the signals? E.g. if some signals are not delivered (e.g. a child process exits, and libuv does not get SIGCHLD), can I expect some reasonable behavior, or is that undefined behavior? Is there a libuv policy for signal handling? I.e. which signals are safe to handle by the user or host environment? Any help or pointers are greatly appreciated, thanks, Gabor -- 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 libuv+unsubscr...@googlegroups.com. To post to this group, send email to libuv@googlegroups.com. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
