From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Signals caught by subtasks
Date: Wed, 22 Apr 1998  0:53:58
Organization: Aspen Technology, Inc.
Lines: 11
Message-ID: <353d3fa6.sandmann@clio.rice.edu>
References: <353C848D DOT 41022A02 AT usa DOT net>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: dmcap2.aco.aspentech.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

> If a DJGPP app launches a subtask, which is also a DJGPP app, and this then
> catches SIGSEGV or another fatal signal, does this propagate all the way back to
> leave the stunned user staring at a C:\ prompt? Or does the parent task simply
> get a task returned with exit code 255?

The task returns with an exit code, unless the child does something so bad
that it corrupts something in the DPMI provider or somesuch.

The CTRL-C and CTRL-BREAK signal is actually seen by all processes in the
chain and each will act on it individually depending on the state of the
signal handler for that process and/or libc settings.