Lines Matching refs:cause

52 * Kinds of Signals::            Some examples of what can cause a signal.
62 of the events that can cause (or @dfn{generate}, or @dfn{raise}) a
187 cause of termination by examining the termination status code reported
255 signal that happened and then reraising it; this will cause the program
265 The default action for all of these signals is to cause the process to
448 this will cause the program to terminate with that signal, as if it had
451 The (obvious) default action for all of these signals is to cause the
457 The @code{SIGTERM} signal is a generic signal used to cause program
498 The @code{SIGKILL} signal is used to cause immediate program termination.
506 it a @code{SIGKILL} signal will almost always cause it to go away.
536 @xref{Setting an Alarm}, for information about functions that cause
539 The default behavior for these signals is to cause program termination.
732 them is to cause the process to terminate.
748 Another cause of @code{SIGPIPE} is when you try to output to a socket
1468 Handler functions that terminate the program are typically used to cause
1842 them cause the same problem.  Function descriptions in this manual
2087 that handler will cause @code{EINTR}.  @xref{Flags for Sigaction}.
2110 This might at first appear to cause unreliable behavior on
2867 middle.  But that does not cause any problem.  If the signal happens