Adopey.146 net.bugs.4bsd utcsrgv!utzoo!decvax!duke!mcnc!unc!dopey.smb Thu Mar 11 13:03:48 1982 sigset botch If a sighold is done, a subsequent sigset call will return SIG_HOLD rather than a routine address. An attempt to use this value will store a bad address -- 3! -- so that any occurrence of the signal will send the program flaming down the tubes. That is, a sequence like this will fail (miserably): sighold(SIGINT); ... s = sigset(SIGINT, myint); .... sigset(SIGINT, s); It's a problem because closed subroutine often like to take their own actions with knowing the current state of affairs. I've tripped over this in some versions of ucbmail. ----------------------------------------------------------------- gopher://quux.org/ conversion by John Goerzen of http://communication.ucsd.edu/A-News/ This Usenet Oldnews Archive article may be copied and distributed freely, provided: 1. There is no money collected for the text(s) of the articles. 2. The following notice remains appended to each copy: The Usenet Oldnews Archive: Compilation Copyright (C) 1981, 1996 Bruce Jones, Henry Spencer, David Wiseman.