28 Aug
2009
28 Aug
'09
4:15 p.m.
Moritz escribió:
Hello Ion.
Thanks for the quick response. I am working with boost version 1.37 and it looks like I have found the bug you described. Thank you very much. Another question concerning this topic is if there is a possibility to remove managed_shared_memory, named_mutexes or message_queues by force, that means no matter if there are processes that have mapped the memory or are working with the mutexes.
Latest Boost versions' (1.39, 1.40) ::remove() works that way (unix way, you can unlink an in-use file) in Windows. Best, Ion