Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!yale!gumby!wupost!howland.reston.ans.net!agate!agate.berkeley.edu!cgd From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) Newsgroups: comp.os.386bsd.bugs Subject: Re: cvs 1.3 bugfix Date: 4 Mar 93 17:45:50 Organization: Kernel Hackers 'r' Us Lines: 20 Message-ID: <CGD.93Mar4174550@eden.CS.Berkeley.EDU> References: <RICH.93Mar3114046@omicron.Rice.edu> <SOMMERFELD.93Mar3180839@blatt.apollo.hp.com> <RICH.93Mar3233616@omicron.Rice.edu> NNTP-Posting-Host: eden.cs.berkeley.edu In-reply-to: rich@Rice.edu's message of Thu, 4 Mar 1993 05:36:16 GMT In article <RICH.93Mar3233616@omicron.Rice.edu> rich@Rice.edu (Richard Murphey) writes: >Yep, the posix spec claims sigismember() should return -1 if signo is >out of range. Perhaps this would be sufficient. Rich an interesting note: cvs works on an HP9k/300, running 4.4, if sighandle.c isn't compiled with -O. with -O it loops infinitely... (this is due to a m68k thing which mod 32's bit numbers for btst... 8-) basically, since sigismember() is not guaranteed to return -1 if the signal number is out of range, CVS should explicitly check this... chris -- Chris G. Demetriou cgd@cs.berkeley.edu MENTALLY CONTAMINATED and proud of it!