Actions
Bug #4328
closedsigprocmask(2) talks about the 'how' argument
Start date:
2013-11-14
Due date:
% Done:
100%
Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:
External Bug:
Description
Here the sigprocmask(2) man page is talking about the 'how' argument (with possible values SIG_BLOCK, SIG_UNBLOCK, SIG_SETMASK), but it is not noted there that we are really talking about 'how':
SYNOPSIS #include <signal.h> int sigprocmask(int how, const sigset_t *restrict set, sigset_t *restrict oset); DESCRIPTION The sigprocmask() function is used to examine and/or change the caller's signal mask. If the value is SIG_BLOCK, the set pointed to by the set argument is added to the current signal mask. If the value is SIG_UNBLOCK, the set pointed by the set argument is removed from the current signal mask. If the value is SIG_SETMASK, the current signal mask is replaced by the set pointed to by the set argument. If the oset argument is not NULL, the previous mask is stored in the space pointed to by oset. If the value of the set argu- ment is NULL, the value how is not significant and the caller's signal mask is unchanged; thus, the call can be used to inquire about currently blocked signals. If the set or oset argument points to an invalid address, the behavior is undefined and errno may be set to EFAULT.
Updated by Marcel Telka over 8 years ago
- Status changed from New to In Progress
- Assignee set to Marcel Telka
Updated by Marcel Telka over 8 years ago
- Subject changed from sigprocmask(2): Talking about 'how', but do not confess so to sigprocmask(2) talks about the 'how' argument
Updated by Marcel Telka over 8 years ago
- Status changed from In Progress to Pending RTI
Updated by Electric Monk over 8 years ago
- Status changed from Pending RTI to Closed
- % Done changed from 0 to 100
git commit 3689c709de099274714d61c877dcc1aa333f3f41
commit 3689c709de099274714d61c877dcc1aa333f3f41 Author: Marcel Telka <marcel.telka@nexenta.com> Date: 2014-11-24T21:42:00.000Z 4328 sigprocmask(2) talks about the 'how' argument Reviewed by: Richard Lowe <richlowe@richlowe.net> Reviewed by: Gordon Ross <gordon.ross@nexenta.com> Reviewed by: Yuri Pankov <yuri.pankov@nexenta.com> Approved by: Dan McDonald <danmcd@omniti.com>
Actions