Within the locked critical region I do a timed wait on a condition variable. The mutex falls to unlock only if the timed wait on the condition variable timed out. If the condition is met, then the mutex unlocks when it goes out of scope.

Maybe the shmem library is using a single flag for the status of a mutex and condition variable (seems unlikely though).

On 24/05/06, Steven Wooding <steve.apo@googlemail.com> wrote:

Hi,

I wonder if you can help me.

I'm using the Shmem library (v0.92) and I'm trying to use a shared_timed_mutex with a scoped_timed_lock. This seems to work until the mutex is about to go out of scope. Then my program just hangs. It seems that it can not unlock the mutex. I tried issuing a "unlock" function call on the lock object and that hangs as well.

Could anyone confirm if the shared_timed_mutex works at the moment.

Thanks for you help.

Steve.