*Note that you must not use sigprocmask in multi-threaded processes, because each thread has its own signal mask and there is no single process signal mask. According to POSIX, the behavior of sigprocmask in a multi-threaded process is “unspecified”. *
There is a lot more to signal handling than sigprocmask. If you read through all the docs, you should be able to work out what you want to do. On Tue, Aug 13, 2019 at 5:27 PM hui zhang <fastfad...@gmail.com> wrote: > check this > https://groups.google.com/forum/#!topic/golang-nuts/1YvP-5V6xSI > when we code golang with c, some c code used * sigwait sigwaitinfo* > function to wait signal. > sometime this signal is caught by golang runtime, and this cause cash. > we want the signal continue to be handled by *sigwait sigwaitinfo* > > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/086f1e16-c8ea-4970-b4e8-98b34c4dec75%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/086f1e16-c8ea-4970-b4e8-98b34c4dec75%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAFZPyg1zoTFAAhM%3Dn2gjujOKH1eK%2BHUHS6jdrjgTQ4kt6Ydtcg%40mail.gmail.com.
