This is the mail archive of the
mailing list for the Cygwin project.
Re: G++ guru's please comment - Re: FW: pthread_create problem in Cygwin 1.1.8-2]
----- Original Message -----
From: "Christopher Faylor" <firstname.lastname@example.org>
Sent: Tuesday, April 10, 2001 12:39 AM
Subject: Re: G++ guru's please comment - Re: FW: pthread_create problem
in Cygwin 1.1.8-2]
> 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,
> >guaranteed if two or more threads enter a try block concurrently).
> >Something in g++ is dsiabled when it's built without thread support,
> >it returns the same base address for the context struct for each
> >That function should return a different context regardless IMO,
> >they are using pthread_key_create, which I have also implemented.
> >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
> we were still waiting on final word on newlib reorganization.
I mailed cygwin-patches late last night. The final word is
a) Don't alter RTEMS types yet.
b) Do what I started to do and split the types into separate files. If
we have time to do RTEMS great.
c) cygwin should look at using the newlib pthread.h include (which we
As my patch is a step in the right direction, I see no issue with it
going in, and later work completing the rearrangement.
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple