Lines Matching defs:signal
6 Package signal implements access to incoming signals.
21 synchronous signal into a run-time panic.
27 Of the asynchronous signals, the SIGHUP signal is sent when a program
28 loses its controlling terminal. The SIGINT signal is sent when the
30 which by default is ^C (Control-C). The SIGQUIT signal is sent when
38 By default, a synchronous signal is converted into a run-time panic. A
39 SIGHUP, SIGINT, or SIGTERM signal causes the program to exit. A
40 SIGQUIT, SIGILL, SIGTRAP, SIGABRT, SIGSTKFLT, SIGEMT, or SIGSYS signal
42 SIGTTOU signal gets the system default behavior (these signals are
43 used by the shell for job control). The SIGPROF signal is handled
48 (signal handler set to SIG_IGN), they will remain ignored.
50 If the Go program is started with a non-empty signal mask, that will
56 modified signal mask.
77 is called for either signal, a signal handler will be installed for
78 that signal and it will no longer be ignored. If, later, Reset or
79 Ignore is called for that signal, or Stop is called on all channels
80 passed to Notify for that signal, the signal will once again be
82 signal, while Ignore will cause the system to ignore the signal
85 If the program is started with a non-empty signal mask, some signals
87 for a blocked signal, it will be unblocked. If, later, Reset is
88 called for that signal, or Stop is called on all channels passed to
89 Notify for that signal, the signal will once again be blocked.
94 SIGPIPE signal.
99 error) will cause the program to exit with a SIGPIPE signal. A write
101 the SIGPIPE signal, and the write will fail with an EPIPE error.
104 descriptor number does not matter. The SIGPIPE signal will be
116 configures the signal handlers as expected by the Go runtime, before
118 install its own signal handlers, it must take certain steps to keep Go
120 effect changes to signal handler settings by the non-Go code can have
124 If the non-Go code called by the Go program does not change any signal
128 If the non-Go code installs any signal handlers, it must use the
130 the program to crash if the signal is received. Go programs routinely
131 run with a limited stack, and therefore set up an alternate signal
132 stack. Also, the Go standard library expects that any signal handlers
136 If the non-Go code installs a signal handler for any of the
138 the existing Go signal handler. If those signals occur while
139 executing Go code, it should invoke the Go signal handler (whether the
140 signal occurs while executing Go code can be determined by looking at
141 the PC passed to the signal handler). Otherwise some Go run-time
144 If the non-Go code installs a signal handler for any of the
145 asynchronous signals, it may invoke the Go signal handler or not as it
146 chooses. Naturally, if it does not invoke the Go signal handler, the
148 the SIGPROF signal in particular.
150 The non-Go code should not change the signal mask on any threads
152 its own, it may set the signal mask as it pleases.
154 If the non-Go code starts a new thread, changes the signal mask, and
158 SIGSETXID. When the Go function returns, the non-Go signal mask will
161 If the Go signal handler is invoked on a non-Go thread not running Go
162 code, the handler generally forwards the signal to the non-Go code, as
163 follows. If the signal is SIGPROF, the Go handler does
165 signal, and raises it again, to invoke any non-Go handler or default
173 have already installed signal handlers when the Go code starts (that
180 If the Go runtime sees an existing signal handler for the SIGCANCEL or
182 the SA_ONSTACK flag and otherwise keep the signal handler.
185 signal handler. It will save any existing signal handler. If a
186 synchronous signal arrives while executing non-Go code, the Go runtime
187 will invoke the existing signal handler instead of the Go signal
191 not install any other signal handlers by default. If there is an
192 existing signal handler, the Go runtime will turn on the SA_ONSTACK
193 flag and otherwise keep the signal handler. If Notify is called for an
194 asynchronous signal, a Go signal handler will be installed for that
195 signal. If, later, Reset is called for that signal, the original
196 handling for that signal will be reinstalled, restoring the non-Go
197 signal handler if any.
200 install a signal handler for the asynchronous signals listed above,
201 and save any existing signal handler. If a signal is delivered to a
203 an existing non-Go signal handler, that handler will be installed
204 before raising the signal.
221 package signal
