Date:	Wed, 14 Jan 1998 11:39:42 +0000 (GMT)
From:	George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp AT delorie DOT com
Subject:	Re: Request for comments: SIGQUIT in DJGPP v2.02
In-Reply-To:	<Pine.SUN.3.91.980114130829.8730B-100000@is>
Message-ID:	<Pine.OSF.3.95.980114111714.30690C-100000@sable.ox.ac.uk>
MIME-Version:	1.0

On Wed, 14 Jan 1998, Eli Zaretskii wrote:

> Or are you bothered by the fact that calling "raise(SIGQUIT)" will
> have no effect when the SIGQUIT handler is set to SIG_DFL?  If so,
> then I don't understand why is that a problem.  If SIGQUIT is
> *documented* to be ignored by default, then a program which wants
> SIGQUIT to abort will need to install a handler to do that (I'm
> planning on writing such a handler that users could install without
> having to invent it).  It's analogous to the case of SIGWINCH
> (generated on Unix when dimensions of the X window are changed): its
> default action is to be discarded, and so "raise(SIGWINCH)" does
> nothing.

Okay I see.  I'd always assumed that raising SIGQUIT should terminate the
program by default, but I suppose just because that's common behaviour
it doesn't mean it's obligatory ;). 

-- 
Regards,

george DOT foot AT merton DOT oxford DOT ac DOT uk

- Raw text -