Mail Archives: cygwin-developers/2002/07/03/14:51:25

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: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <05bd01c222c2$e398d8c0$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: <cygwin-developers AT cygwin DOT com>
Subject: Protected handle errors
Date: Wed, 3 Jul 2002 19:53:15 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

A while ago I posted that I was seeing lots of messages like the
following when running a cygwin DLL compiled with --enable-debugging:

19791 [main] sh 1316 mark_closed: attempt to close protected handle
void memory_init():155(cygwin_mount_h<0x150>)
24806 [main] sh 1316 mark_closed:  by int

I've changed the cygserver client code so the DLL no longer connects
to cygserver at start-up; rather it now delays making a connection
until (and only if) the client actually requires some cygserver
functionality. Hey presto!  I stop seeing these messages.  To be
accurate, I only see them in processes that *do* connect to cygserver
for, e.g., tty handle duplication.

Since I'm also getting some intermittent problems with clients
connecting to cygserver, I thought I ought to investigate this now I
know it's related to cygserver.  Has anyone got any pointers or
suggestions before I go and dive in?  I assume that the cygserver
client code should be doing something with the IPC handles that it's
presently not doing.

// Conrad

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019