Lines Matching full:will
20 general, except as discussed below, Go programs will convert a
45 signals will be caught but no action will be taken.
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
55 started by os.Exec, or by the os/exec package, will inherit the
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
80 passed to Notify for that signal, the signal will once again be
81 ignored. Reset will restore the system default behavior for the
82 signal, while Ignore will cause the system to ignore the signal
86 will be explicitly unblocked as described above. If Notify is called
87 for a blocked signal, it will be unblocked. If, later, Reset is
89 Notify for that signal, the signal will once again be blocked.
93 When a Go program writes to a broken pipe, the kernel will raise a
99 error) will cause the program to exit with a SIGPIPE signal. A write
100 to a broken pipe on some other file descriptor will take no action on
101 the SIGPIPE signal, and the write will fail with an EPIPE error.
104 descriptor number does not matter. The SIGPIPE signal will be
105 delivered to the Notify channel, and the write will fail with an EPIPE
108 This means that, by default, command line programs will behave like
109 typical Unix command line programs, while other programs will not
133 will use the SA_RESTART flag. Failing to do so may cause some library
142 panics will not occur as expected.
147 Go behavior described above will not occur. This can be an issue with
155 then invokes a Go function in that thread, the Go runtime will
158 SIGSETXID. When the Go function returns, the non-Go signal mask will
171 When Go code is built with options like -buildmode=c-shared, it will
176 will initialize signals at global constructor time. For
177 -buildmode=c-shared the Go runtime will initialize signals when the
181 SIGSETXID signals (which are used only on GNU/Linux), it will turn on
184 For the synchronous signals and SIGPIPE, the Go runtime will install a
185 signal handler. It will save any existing signal handler. If a
187 will invoke the existing signal handler instead of the Go signal
190 Go code built with -buildmode=c-archive or -buildmode=c-shared will
192 existing signal handler, the Go runtime will turn on the SA_ONSTACK
194 asynchronous signal, a Go signal handler will be installed for that
196 handling for that signal will be reinstalled, restoring the non-Go
199 Go code built without -buildmode=c-archive or -buildmode=c-shared will
202 non-Go thread, it will act as described above, except that if there is
203 an existing non-Go signal handler, that handler will be installed
210 will cause os.Interrupt to be sent on the channel, and the program will
212 to Notify, then the default behavior will be restored.
217 Notify with a syscall.Note will cause that value to be sent on the