| delorie.com/archives/browse.cgi | search |
----- Original Message ----- From: "egor duda" <deo AT logos-m DOT ru> To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> Cc: <cygwin-developers AT cygwin DOT com> Sent: Monday, November 19, 2001 1:37 AM Subject: Re: pthread_mutex_init fails > Hi! > > Sunday, 18 November, 2001 Robert Collins robert DOT collins AT itdomain DOT com DOT au wrote: > > RC> ----- Original Message ----- > RC> From: "egor duda" <deo AT logos-m DOT ru> > > >> the problem remains that the patched code still won't work on w95, but > >> the current code doesn't work at all! > > RC> The current code should run fine on w95 and 2k - it did for me before > RC> committing it 0 I tested on both 9x and 2k. > > RC> However the bug is likely the cause for Jasons continued python > RC> failures. > > really? have you checked if exactly one thread wakes up when condition > variable is signaled? i _can't_ see how current code can work at all. > please run winsup.api/pthread/condvar3_1.c test on w2k and tell what > the result is. btw, are you sure you've been testing on stock w95? or > it was w98? or osr2? msdn says that InterlockedIncrement() behavior > changed from w95 to w98 and from nt3.5 to nt4.0. > > again, i can't see how current code can work at all either on w95 or > on w98 or on nt or on w2k. what exactly have you tested? 95 OSR 2 and W2k SP2. Why can't it work? I haven't checked that _only_ one thread wakes up no, but the woken threads are serialised regardless. I agree there is a big bug here. Rob
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |