This is the mail archive of the
cygwin-patches@cygwin.com
mailing list for the Cygwin project.
Re: fix cond_race... was RE: src/winsup/cygwin ChangeLog thread.cc thread.h ...
- To: Robert Collins <robert dot collins at itdomain dot com dot au>
- Subject: Re: fix cond_race... was RE: src/winsup/cygwin ChangeLog thread.cc thread.h ...
- From: Jason Tishler <jason at tishler dot net>
- Date: Mon, 8 Oct 2001 22:01:00 -0400
- Cc: cygwin-patches at cygwin dot com
Rob,
On Sun, Oct 07, 2001 at 10:24:30PM +1000, Robert Collins wrote:
> As for you, you are stopping in the same place. Can you give me your
> system config - Processor count & speed?
Single PIII, 500 MHz and 320 MB RAM.
> Are you able to try SP 2?
I can but would prefer to hold off until we better understand this
problem.
> > FWIW, I built from CVS on 10/5/2001 and I'm running under Win2K SP1.
>
> Thats certainly recent enough, and the SP _shouldn't_ :] matter.
>
> I'm going to have to think about this one - unless your systems is
> massively overloaded during the test - such that the spinloop around
> line 482 is able to get 10 timeslices without the waiting thread getting
> 1?!? - there should be no way to tickle this.
I don't think that my system is "massively overloaded" because I can
still do other work while running this test. However, Task Manager does
report "100%" CPU usage.
> I'd like you to add a system_printf, at line 483, something like
> "system_printf ("repulsing event at count 5\n"); (oh, and put it at the
> PulseEvent in {}. If that fires then we know that the detection code is
> ok. If so, can you try bumping the spin count up, and make the pulsevent
> fire if spins mod 5 == 0 ?
Your line numbers don't agree with thread.cc version 1.52, but I think I
know where to add the printfs. I will try this and report back ASAP.
Please note that I just started a new job with a nasty commute so it may
be a few days before I can sneak some time.
Thanks,
Jason