Re: [Mingw-w64-public] Deadlock in winpthreads' pthread_cond_signal()

2018-03-10 Thread Liu Hao
在 2018/3/10 20:46, Sitsofe Wheeler 写道: > On 10 March 2018 at 12:38, Liu Hao wrote: >> 在 2018/3/10 20:06, Sitsofe Wheeler 写道: >>> Reattaching example program with .txt extension and just in case you >>> can also download it from http://sucs.org/~sits/test/signalhang.c . >>> >> >>

Re: [Mingw-w64-public] Deadlock in winpthreads' pthread_cond_signal()

2018-03-10 Thread Sitsofe Wheeler
On 10 March 2018 at 12:38, Liu Hao wrote: > 在 2018/3/10 20:06, Sitsofe Wheeler 写道: >> Reattaching example program with .txt extension and just in case you >> can also download it from http://sucs.org/~sits/test/signalhang.c . >> > > This seems not producible on my Windows 7, but

Re: [Mingw-w64-public] Deadlock in winpthreads' pthread_cond_signal()

2018-03-10 Thread Sitsofe Wheeler
On 10 March 2018 at 10:37, Liu Hao wrote: > 在 2018/3/10 18:14, Sitsofe Wheeler 写道: >> Hi, >> >> It's possible to trigger a deadlock in winpthreads' >> pthread_cond_signal() when using the pthread_cond_signal() call >> outside of a pthread_mutex_lock()/pthread_mutex_unlock()

Re: [Mingw-w64-public] Deadlock in winpthreads' pthread_cond_signal()

2018-03-10 Thread Liu Hao
在 2018/3/10 18:14, Sitsofe Wheeler 写道: > Hi, > > It's possible to trigger a deadlock in winpthreads' > pthread_cond_signal() when using the pthread_cond_signal() call > outside of a pthread_mutex_lock()/pthread_mutex_unlock() region. This > problem happens under Windows 2012 R2 with

Re: [Mingw-w64-public] GCC Fallthrough warnings.

2018-03-10 Thread jpmugaas
-Original Message- From: Mateusz Mikuła Sent: Friday, March 9, 2018 7:41 PM To: mingw-w64-public@lists.sourceforge.net Subject: Re: [Mingw-w64-public] GCC Fallthrough warnings. There is no patch attached. I hope this works: === diff --git

[Mingw-w64-public] Deadlock in winpthreads' pthread_cond_signal()

2018-03-10 Thread Sitsofe Wheeler
Hi, It's possible to trigger a deadlock in winpthreads' pthread_cond_signal() when using the pthread_cond_signal() call outside of a pthread_mutex_lock()/pthread_mutex_unlock() region. This problem happens under Windows 2012 R2 with winpthreads-5.0.3 (Cygwin64) and winpthreads-7.2.0 (standalone)