This is the mail archive of the
cygwin-patches@cygwin.com
mailing list for the Cygwin project.
Re: Deadly embrace between pthread_cond_wait and pthread_cond_signal
- To: Norman Vine <nhv at cape dot com>
- Subject: Re: Deadly embrace between pthread_cond_wait and pthread_cond_signal
- From: Jason Tishler <Jason dot Tishler at dothill dot com>
- Date: Tue, 26 Jun 2001 10:33:50 -0400
- Cc: "'Robert Collins'" <robert dot collins at itdomain dot com dot au>, "'Greg Smith'" <gsmith at nc dot rr dot com>, cygwin-patches at cygwin dot com
- Organization: Dot Hill Systems Corp.
Norman,
On Tue, Jun 26, 2001 at 10:27:49AM -0400, Norman Vine wrote:
> Since my last correspondance with Jason I have tested this with
> the 'stock' Python-2.1 tarball and all seems to be OK
How long does it take to run the regression tests (sans test_poll)?
> I am experiencing an occasional 'hang' in the make process
> this is on WIn2k sp2 and the 'very latest' Cygwin files.
> Usually a 'ctrl-C' will abort the make and a subsequent make
> will run to completion. This make behaviour is not isolated to the
> Python build but I have not been able to find a situation that will
> reliably reproduce it.
FWIW, I am experiencing the "hang" under Windows NT 4.0 SP5. However,
for me, the hang is with Python (with threads) and not make itself.
IIRC, during the make I see two python processes. After killing the
make, I still see one python process that needs to be manually killed.
Please do a ps before and after you kill the make. Are you observing
this behavior or something different?
Thanks,
Jason
--
Jason Tishler
Director, Software Engineering Phone: 732.264.8770 x235
Dot Hill Systems Corp. Fax: 732.264.8798
82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com