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:	Thu, 1 Aug 2002 10:52:36 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: RFC: TLS problem
Message-ID:	<20020801145236.GC18385@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<Pine DOT WNT DOT 4 DOT 44 DOT 0208011634350 DOT 331-100000 AT algeria DOT intern DOT net>
Mime-Version:	1.0
In-Reply-To:	<Pine.WNT.4.44.0208011634350.331-100000@algeria.intern.net>
User-Agent:	Mutt/1.3.23.1i

On Thu, Aug 01, 2002 at 04:48:09PM +0200, Thomas Pfaff wrote:
>IMHO the are two possible solutions:
>1. Synchronize the win32 TLS array between parent and child.
>2. Create a cygwin only solution that will use its own tls array like CGFs
>experimental TLS implementation.

My TLS implementation only provides a limited amount of per-thread storage.
It wasn't intended for generic use, just use within the cygwin DLL.

So, it sounds like 1. is the only feasible solution.

cgf

- Raw text -