Date:	Tue, 2 Feb 1999 10:46:12 -0500
Message-Id:	<199902021546.KAA00724@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp AT delorie DOT com
In-reply-to:	<3.0.6.32.19990202002923.008bd370@pop.netaddress.com> (message
	from Paul Derbyshire on Tue, 02 Feb 1999 00:29:23 -0500)
Subject:	Re: Clarification re: signals
References:	<3 DOT 0 DOT 6 DOT 32 DOT 19990202002923 DOT 008bd370 AT pop DOT netaddress DOT com>
Reply-To:	djgpp AT delorie DOT com

These don't all apply to DJGPP, but...

> SIGKILL    -- Does this pop upwhen a process receives kill()?

No, SIGKILL is the only signal a process can't catch, so it's the
"kill of last resort" to try to end a process.  SIGKILL can only be
sent, not trapped.  The kill() function can send *any* signal to a
process.

> SIGQUIT    -- ???

Not sure about this one, but I think it can sometimes be generated
from the keyboard under Unix.

> SIGTERM    -- ???

Ctrl-C generates this.

> SIGILL     -- ???

This usually implies that the CPU has attempted to execute an
ill-formed opcode, like random garbage.

- Raw text -