You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2004/08/28 18:58:09 UTC
DO NOT REPLY [Bug 27654] -
Deadlock in apr_thread_cond_wait on WIN32 platform
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27654>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27654
Deadlock in apr_thread_cond_wait on WIN32 platform
------- Additional Comments From klaus.keppler@informatik.stud.uni-erlangen.de 2004-08-28 16:58 -------
There's a general problem when calling apr_mutex_unlock several times under
WIN32; since this might call the WIN32 API function "LeaveCriticalSection".
Quoting MSDN docs on LeaveCriticalSection:
---snip---
[...]
If a thread calls LeaveCriticalSection when it does not have ownership of the
specified critical section object, an error occurs that may cause another
thread using EnterCriticalSection to wait indefinitely.
[...]
---snip---
However - this patch removes problems when using condvars under WIN32.
Another solution would be to add a "lock counter" to APR mutexes.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org