Re: [Boost-users] [Interprocess] hang locking p_hdr->m_mutex

Subject: Re: [Boost-users] [Interprocess] hang locking p_hdr->m_mutex
From: David Byron (dbyron_at_[hidden])
Date: 2011-08-26 19:25:18

On 8/26/2011 9:56 AM, Ion Gaztañaga wrote:
> El 26/08/2011 14:40, David Byron escribió:
>
>> If CreateMutex behaves the "right way" on windows, does it make sense to
>> have the behavior differ across platforms?
>
> Portability is the most important goal for Interprocess :(

Makes sense.  I'm not hell bent on changing it.  I'd love to use it just 
as it is.  I just can't figure out how to do it safely given that a 
process might die while holding the interprocess_mutex.  I could easily 
be missing something.  If someone would tell me if that's the case, I'd 
be eternally grateful.

> And CreateMutex needs a name, you can't construct a named mutex in
> shared memory, both are different beasts.

 From http://msdn.microsoft.com/en-us/library/ms682411%28v=vs.85%29.aspx:

"Multiple processes can have handles of the same mutex object, enabling 
use of the object for interprocess synchronization."

and then:

"A process can specify a named mutex in a call to the OpenMutex or 
CreateMutex function to retrieve a handle to the mutex object."

The name of the message queue seems OK, perhaps beginning with "Global\" 
on some versions of windows.

So I still think windows mutexes would work.

-DB