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: Fri, 20 Sep 2002 01:32:05 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Recent change to init.cc for thread detach looks wrong?
Message-ID: <20020920053205.GA20330@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i

Robert,
Your recent change:
2002-09-11  Robert Collins  <rbtcollins AT hotmail DOT com>

        * init.cc (dll_entry): On thread detach, if the thread hasn't
        exit()ed, do so.

doesn't look right.  The code invokes pthread::exit which can block
waiting on a mutex, it seems.

Since the thread attach and detach code is, I believe, forced to
be single thread (i.e., no other threads are scheduled), this
can lead to some hangs.

I've been seeing some defunct, unkillable processes recently in
cygwin.  I wonder if this is the cause.

cgf