home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!usc!news.service.uci.edu!ucivax!ucla-cs!twinsun!eggert
- From: eggert@twinsun.com (Paul Eggert)
- Subject: Re: bug in CVS-1.3 or <signal.h>:__sigmask
- Message-ID: <bkL#Ot~Z@twinsun.com>
- Sender: usenet@twinsun.com
- Supersedes: <bkLqw5XV@twinsun.com>
- Nntp-Posting-Host: farside
- Organization: Twin Sun Inc, El Segundo, CA, USA
- X-Newsreader: NN version 6.4.19
- References: <1993Jan22.142240.16071@infodev.cam.ac.uk>
- Date: Sat, 23 Jan 1993 03:33:18 GMT
- Lines: 11
-
- ijackson@nyx.cs.du.edu (Ian Jackson) writes:
-
- Unfortunately I don't have access to any POSIX documentation to find
- out which of <signal.h> and CVS is right (ie, whether CVS is allowed
- to pass to sigismember a signal number which is out of range), so I
- don't know which file to patch.
-
- Linux is the one that's wrong. Posix 1003.1-1990 section 3.3.3.4 says that
- sigismember need not detect signals out of range; but section 2.4 says
- that if sigismember doesn't detect an error, it must succeed.
- Going into an infinite loop isn't success.
-