Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID:	<021801c0b8d8$67a70660$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	signals and fhandlers
Date:	Fri, 30 Mar 2001 15:15:14 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	30 Mar 2001 05:09:56.0764 (UTC) FILETIME=[A980BDC0:01C0B8D7]

I've finished the fifo support logic and code. (based on test results
from openBSD for the expected behaviour).

I need to _guarantee_ that the close() routine for the fhandler will get
called even if the process terminates due to a signal.

Is that automatically taken care of once I put the code in cygwin1.dll
rather than as an external test program?

Rob

- Raw text -