![]() SA_NOCLDWAIT Ĭauses implementations not to create zombie processes on child death. SA_SIGINFO Ĭauses extra information to be passed to signal handlers at the time of receipt of a signal. SA_RESTART Ĭauses certain functions to become restartable. SA_RESETHAND Ĭauses signal dispositions to be set to SIG_DFL on entry to signal handlers. SA_ONSTACK Ĭauses signal delivery to occur on an alternate stack. The resulting set is the signal set pointed to by the argument set. ![]() The resulting set is the intersection of the current set and the complement of the signal set pointed to by the argument The resulting set is the union of the current set and the signal set pointed to by the argument set. The following shall be declared as constants: SA_NOCLDSTOP Do The storage occupied by sa_handler and sa_sigaction may overlap, and a conforming application shall not use both Void (*sa_sigaction)(int, siginfo_t *, void *) Sigset_t sa_mask Set of signals to be blocked during execution of the signal handling function. Header shall provide a declaration of struct sigaction, including at least the following members: void (*sa_handler)(int) Pointer to a signal-catching function or one of the macros SIG_IGN or SIG_DFL. C Continue the process, if it is stopped otherwise, ignore the signal. A Abnormal termination of the process.Īdditionally, implementation-defined abnormal termination actions, such as creation of a core file, may occur. The process is terminated with all the consequences of _exit() except that the status made available to wait() and waitpid() indicates abnormal The default actions are as follows: T Abnormal termination of the process. High bandwidth data is available at a socket. Stop executing (cannot be caught or ignored). ![]() The following signals shall be supported on all implementations (default actions are explained below the table):Īccess to an undefined portion of a memory object. ISO C standard only requires the signal names SIGABRT, SIGFPE, SIGILL, SIGINT, SIGSEGV, and SIGTERM to be defined. Additional implementation-defined signals may occur in the The value 0 is reserved for use as the null Each of the signals have distinct positive integer values. Signals defined hereīegin with the letters SIG. This header also declares the constants that are used to refer to the signals that occur in the system. It is implementation-defined whether realtime signal behavior is supported for other signals. The range SIGRTMIN through SIGRTMAX inclusive shall include at least signal numbers. The signal numbers in this range do not overlap any of the signals specified in the Signal numbers that are reserved for application use and for which the realtime signal behavior specified in this volume of This header shall also declare the macros SIGRTMIN and SIGRTMAX, which evaluate to integer expressions, and specify a range of The sigval union shall be defined as: int sival_int Integer signal value. SIGEV_THREAD A notification function is called to perform notification. SIGEV_SIGNAL A queued signal, with an application-defined value, is generated when the event of interest occurs. The following values of sigev_notify shall be defined: SIGEV_NONE No asynchronous notification is delivered when the event of interest occurs. (pthread_attr_t *) sigev_notify_attributes Notification attributes. ![]() Void(*)(union sigval) sigev_notify_function Notification function. The header shall define the sigevent structure, which has at least the following members: int sigev_notify Notification type. Integer or structure type of an object used to represent sets of signals. The following data types shall be defined through typedef: sig_atomic_t Possibly volatile-qualified integer type of an object that can be accessed as an atomic entity, even in the presence of SIG_ERR Return value from signal() in case of error. SIG_DFL Request for default signal handling. Whose value matches no declarable function. The header shall define the following symbolic constants, each of which expands to a distinct constant The appropriate feature test macro (see the System Interfaces volume of IEEE Std 1003.1-2001, Section 2.2, The Compilation Environment) to enable the visibility of these symbols in this Some of the functionality described on this reference page extends the ISO C standard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |