Re: WaitForSingleObject() will not deadlock
- From: Frank Cusack <fcusack@xxxxxxxxxxx>
- Date: Sun, 01 Jul 2007 18:18:20 -0700
On Sun, 1 Jul 2007 17:01:07 -0700 "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx> wrote:
This is just a CRITICAL_SECTION rough equivalent.
Sorry to be following up so many times when once would have been
sufficient. I don't know the semantics of CRITICAL_SECTION, but
POSIX mutexes provide memory visibility guarantees that, from the
name of it, CRITICAL_SECTION doesn't sound like it does.
They are different beasts.
-frank
.
- Follow-Ups:
- Re: WaitForSingleObject() will not deadlock
- From: Alexander Grigoriev
- Re: WaitForSingleObject() will not deadlock
- From: Doug Harrison [MVP]
- Re: WaitForSingleObject() will not deadlock
- References:
- Re: WaitForSingleObject() will not deadlock
- From: Joseph M . Newcomer
- Re: WaitForSingleObject() will not deadlock
- From: Frank Cusack
- Re: WaitForSingleObject() will not deadlock
- From: Joseph M . Newcomer
- Re: WaitForSingleObject() will not deadlock
- From: Alexander Grigoriev
- Re: WaitForSingleObject() will not deadlock
- Prev by Date: Re: WaitForSingleObject() will not deadlock
- Next by Date: Re: how to switch between property pages using another application?
- Previous by thread: Re: WaitForSingleObject() will not deadlock
- Next by thread: Re: WaitForSingleObject() will not deadlock
- Index(es):