Date: Sun, 20 Oct 1996 16:29:19 +0400 (MSD)
From: "Alexander V. Lukyanov" <lav AT video DOT yars DOT free DOT net>
Message-Id: <199610201229.QAA10580@video.yars.free.net>
To: eliz AT is DOT elta DOT co DOT il, fighteer AT cs DOT com
Cc: djgpp-workers AT delorie DOT com, grendel AT ananke DOT amu DOT edu DOT pl
Subject: Re: Install thingy

> > BTW, is the fact that a generated SIGINT terminates ALL programs in an
> > execution chain simultaneously unless one of them handles it a feature
> > or a bug?  Just curious...
> 
> It's a feature.  Unix works in this way (i.e., the parent gets the 
> signals of its children unless it takes specific action not to), so DJGPP 
> does that also, since it's relatively easy.  The latest port of GNU Make 
> 3.75 uses this to correctly say "Interrupt" when the compilation is 
> interrupted, just like on Unix.
> 
> Note that, unlike Unix, only SIGINT works this way; other signals (such 
> as SIGFPE) don't.

AFAIK, this is not quite correct. In UNIX, parent process does not get
child signals. It is terminal driver who sends SIGINT to *group* of
foreground processes, thus both parent and child get it if they are 
foreground on the same terminal. The same happens with SIGQUIT and
SIGTSTP signals.