Re: [Boost-users] [Interprocess] updating elements in vector of maps fails in optimized code

Please try latest trunk code

I just tried the latest trunk code and I'm sorry to report that the GCC specific attribute does not solve all problems. The crashes or indefinite waits have been resolved though. I also noticed that the described symptoms are not merely a result of compiler optimizations. I was experimenting with different GCC optimization parameters in an attempt to identify the guilty ones when I noticed that even when optimizations are completely turned off, some weird behavior "can" occur. When I run the snippet provided below, compiled with -O0, several times, the program behaves as expected about half of the times and in the other runs, the map find function will fail to find any entries, resulting in a matrix consisting of ones instead of twos. In higher optimization levels, the find function fails consistently. Does the snippet always work for MSVC? kind regards, Steven #include <iostream> #include <stdexcept> #include #include #include #include #define MATSIZE 5 typedef boost::interprocess::managed_shared_memory::segment_manager SegmentManager_t; typedef boost::interprocess::allocator VoidAllocator_t; typedef std::pair MapValue_t; typedef boost::interprocess::allocator MapValueAllocator_t; typedef boost::interprocess::map Map_t; typedef boost::interprocess::allocator MapAllocator_t; typedef boost::interprocess::vector VectorofMaps_t; int main(int argc, char **argv) { VectorofMaps_t::size_type i; int j; Map_t::iterator mapiter; try { boost::interprocess::shared_memory_object::remove("MySharedMemory"); boost::interprocess::managed_shared_memory mfile(boost::interprocess::create_only,"MySharedMemory",65536); VoidAllocator_t alloc_inst (mfile.get_segment_manager()); VectorofMaps_t* pS=mfile.construct(boost::interprocess::anonymous_instance)(MATSIZE,Map_t(std::less<int>(),alloc_inst),alloc_inst); for(i=0;isecond+=1.0; std::cout<<mapiter->second<