|Subject:||Re: Deadlock in signal handler|
|Date:||Thu, 16 Mar 2017 12:10:33 -0400|
Have you considered using the pattern of using a socket for signal handling? Then the signal handler writes a byte or closes the socket. The other end of the socket detects this using select() or equivalent. Can be a unix pipe or network socket, depending on where the endpoints live. Can support threads, processes, and distributed processes, all in a portable manner.Iwould avoid the need for calling gettext routines from the handler.
|[Prev in Thread]||Current Thread||[Next in Thread]|