delorie.com/archives/browse.cgi | search |
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 |
Date: | Wed, 3 Jul 2002 14:58:02 -0400 |
From: | Christopher Faylor <cgf AT redhat DOT com> |
To: | cygwin-developers AT cygwin DOT com |
Subject: | Re: Protected handle errors |
Message-ID: | <20020703185802.GC19459@redhat.com> |
Reply-To: | cygwin-developers AT cygwin DOT com |
Mail-Followup-To: | cygwin-developers AT cygwin DOT com |
References: | <05bd01c222c2$e398d8c0$6132bc3e AT BABEL> |
Mime-Version: | 1.0 |
In-Reply-To: | <05bd01c222c2$e398d8c0$6132bc3e@BABEL> |
User-Agent: | Mutt/1.3.23.1i |
On Wed, Jul 03, 2002 at 07:53:15PM +0100, Conrad Scott wrote: >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 >fhandler_base::close():763(get_handle()<0x150>) > >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. Just calling ProtectHandle or ProtectHandle1 on any handles you create should be sufficient. cgf
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |