Handling core dumps when process is holding boost interprocess lock
Hello,
I am working on application where several multi-threaded processes are
attempting to acquire a lock on the shared memory files managed via boost
interprocess.
It appears that if one of these processes dumps a core while holding a lock
on the shared memory file, all the other processes end up waiting for this
lock to be released.
Any ideas on how this can be overcome? I want to ensure that when a process
that is holding the lock dies, it should ensure that the lock is released.
Thanks,
Raj
--
*Twitter: @Blismedia http://twitter.com/#%21/blismobile
BlisMedia
32 Percy Street,
London W1T 2DE
www.blismedia.com http://www.blismobile.com/**
*** http://www.blismobile.com/*
****[image: Follow on Twitter]* http://twitter.com/#%21/blismobile*[image:
Blis Website]* http://www.blismobile.com/
*This communication is from Blis Media Ltd, a company registered in England
and Wales with registered number 06455773. Its registered office is 32
Percy Street, London W1T 2DE, United Kingdom.*
* *
*This communication contains information that is confidential and may also
be privileged. It is for the exclusive use of the intended recipient(s). If
you are not the intended recipient(s), please (1) notify info@blismedia.com
I actually ran into the same issue. I solved it by using file locks,
instead of named mutexes, because the file lock will be released when the
process crashes.
---
Aaron Wright
From: Rajalakshmi Iyer
participants (2)
-
Aaron_Wright@selinc.com
-
Rajalakshmi Iyer