Date: Fri, 16 Aug 1996 00:00:39 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: jkh@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-lib@freefall.freebsd.org Subject: Re: cvs commit: src/lib/libncurses lib_newterm.c Message-ID: <26979.840178839@time.cdrom.com> In-Reply-To: Your message of "Fri, 16 Aug 1996 08:06:56 %2B0200." <199608160606.IAA04877@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > sigaction had unwonted side-effects. > > I don't trust you. ;-) signal()'s implementation is mainly based on And this coming from the guy who got us to change the 3COM driver at the last minute in 2.1.5? :-) > sigaction(). So if the latter has unwanted side-effects for you that > signal doesn't have, it's probably a programmer's error. I'll be happy to explain the symptoms to you. When I simply cloned one of the existing entries already there for SIGTERM and SIGTSTP (and, just going by the docs for sigaction(), they seem correct), my short C test program worked just fine. When I dynamically loaded my curses library into tclsh and initialized the curses library, however, an incoming SIGWINCH would shoot the tclsh dead. This does not happen if I simply use signal(). Try it for yourself if you don't believe me. :-) Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26979.840178839>