Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <199912070527.XAA27072@mercury.xraylith.wisc.edu>
To: Chris Faylor <cgf AT cygnus DOT com>
cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: (patch) enable signals in dynamically loaded Cygwin DLL 
In-Reply-To: Your message of "Mon, 06 Dec 1999 23:48:15 EST."
             <19991206234815 DOT A21564 AT cygnus DOT com> 
Date: Mon, 06 Dec 1999 23:27:02 -0600
From: Mumit Khan <khan AT nanotech DOT wisc DOT edu>

Chris Faylor <cgf AT cygnus DOT com> writes:
> 
> Note that this probably affects tty initialization too.  It's not just
> signals that are affected, it's any thread that is started during DLL
> initialization.  Since CYGWIN=tty implies the creation of several runtime
> threads, I assume that the problem is manifested there as well.
> 

Yes, it does. In fact, one I/O problem I was having (where the dyn
loaded DLL will crash trying to read from the tty) is fixed after 
this.

I believe I've checked all invocations of makethread, and feel that it's
a safe replacement. Please let me know if you have misgivings about the
synchronization, and if so, I can put it back and only enable that if
!dynamically_loaded.

Regards,
Mumit