Re: signals

[Sam S. <sd...@gn...>]

> * Bruno Haible <oe...@py...t> [2008-05-25 11:11:33 +0200]:
>
>>   1. unblocks some signal, e.g. SIGINT, using sigprocmask,
>
> By the way, all Unix systems nowadays support sigprocmask. (And if they did
> not, you would find a substitute in gnulib. I may even write a substitute for
> sigprocmask on mingw some day.)
>
> 2008-05-25  Bruno Haible  <br...@cl...>
>
> 	* m4/signal.m4 (CL_SIGNALBLOCK): Remove macro.
> 	(CL_SIGNAL_UNBLOCK, CL_SIGNAL_BLOCK_OTHERS, CL_SIGACTION_UNBLOCK):
> 	Assume POSIX signal-blocking.
> 	* unix.d (SIGNALBLOCK_POSIX): Define always.
> 	* spvw.d (main): Assume SIGNALBLOCK_POSIX on Unix.
> 	* spvw_sigint.d (react_on_sigint): Likewise.
> 	* spvw_sigsegv.d (stackoverflow_handler): Likewise.

how about spvw_sigterm.d?
does it need the signal magic from spvw_sigint.d?

-- 
Sam Steingold (http://sds.podval.org/) on Fedora release 8 (Werewolf)
http://palestinefacts.org http://israelunderattack.slide.com
http://openvotingconsortium.org http://truepeace.org
War doesn't determine who's right, just who's left.