Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<091e01c2120f$25e50290$6132bc3e@BABEL>
From:	"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	DuplicateHandle() question
Date:	Wed, 12 Jun 2002 13:46:18 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

[I hope this is sufficiently on-topic for this list.]

I'm looking at the cygserver shm implementation and I've got a Win32 issue
that I wondered if anyone out there might be able to help me with.

The problem is that the server uses DuplicateHandle() to create a handle in
the client process. Then if the server later decides to abort the operation,
how can it close that child handle? Or can't it? If it can't, the server
will have to arrange for the client to close it for itself, which makes the
error handling all the more complex (i.e. send back the offending handle
along with the error response).

Any thoughts? or am I misunderstanding some deep fact about Win32 handles?

// Conrad

- Raw text -