Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 9 Apr 2001 10:39:48 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: G++ guru's please comment - Re: FW: pthread_create problem in Cygwin 1.1.8-2] Message-ID: <20010409103948.A29323@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3AD1A64D DOT 7DC36DF0 AT mip DOT sdu DOT dk> <012001c0c0ed$fe28e910$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <012001c0c0ed$fe28e910$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Mon, Apr 09, 2001 at 10:09:54PM +1000 On Mon, Apr 09, 2001 at 10:09:54PM +1000, Robert Collins wrote: >> The error you get is a result of a race condition on a lookup table >> shared by all threads. The stack is NOT corrupted in any way. > >It's not a race condition per se (timing has nothing to do with it, it's >guaranteed if two or more threads enter a try block concurrently). >Something in g++ is dsiabled when it's built without thread support, and >it returns the same base address for the context struct for each thread. >That function should return a different context regardless IMO, unless >they are using pthread_key_create, which I have also implemented. There >is a patch for that in the cygwin patch list archives, and hopefully >it'll be in CVS soon. Isn't this patch gated on newlib changes? If not, I missed it. I thought we were still waiting on final word on newlib reorganization. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple