This is the code I am using to test this:
#include <iostream>
#include <boost/interprocess/managed_mapped_file.hpp>
#include <boost/container/map.hpp>
#include <boost/interprocess/managed_external_buffer.hpp>
#include <boost/interprocess/allocators/node_allocator.hpp>
#include <boost/container/vector.hpp>
namespace bi = boost::interprocess;
int main() {
bi::managed_mapped_file mmfile(bi::open_or_create, "map_iv.dat", 10000000);
typedef bi::allocator<int, bi::managed_mapped_file::segment_manager> int_allocator;
typedef boost::container::vector<int, int_allocator> MyVec;
typedef std::pair<const std::string, MyVec> MyPair;
typedef std::less<std::string> MyLess;
typedef bi::node_allocator<MyPair, bi::managed_mapped_file::segment_manager> node_allocator_t;
typedef boost::container::map<std::string, MyVec, std::less<std::string>, node_allocator_t> MyMap;
MyMap * mapptr = mmfile.find_or_construct<MyMap>("mymap")(mmfile.get_segment_manager());
(*mapptr)["Hello"].push_back(17);
long long s = mapptr->size();
std::cout << s << ' ';
std::cout << (*mapptr)["World"][0] << ' ';
return 0;
}
I get this error message in Visual Studio 2017:
boost_1_69_0\boost\container\vector.hpp(294): error C2512:
"boost::interprocess::allocator<int,boost::interprocess::segment_manager<CharType,MemoryAlgorithm,IndexType>>::allocator": no appropriate default constructor available
I am trying to get this to run and would be grateful for any help!
The issue is that the vector can't be created without an allocator (basicly it needs to know which segment it should allocate within - it could be different from the segment the map is in). One way to get around this is creating a new type that uses mmfile
global object in a constructor:
bi::managed_mapped_file mmfile(bi::open_or_create, "map_iv.dat", 10000000);
int main() {
typedef bi::allocator<int, bi::managed_mapped_file::segment_manager> int_allocator;
struct MyVec : public boost::container::vector<int, int_allocator>{
MyVec() : boost::container::vector<int, int_allocator>{mmfile.get_segment_manager()}{};
};
//..
}
or you could call emplace
instead of push_back
as shown here.
Besides that, Im guessing it's a mistake to use std::string
in mapped_file - just a note though. The following is from a boost example - which has been modified to use the same data structure while also allocating the string in the segment:
#include <boost/interprocess/managed_shared_memory.hpp>
#include <boost/interprocess/allocators/allocator.hpp>
#include <boost/interprocess/containers/map.hpp>
#include <boost/interprocess/containers/vector.hpp>
#include <boost/interprocess/containers/string.hpp>
int main ()
{
using namespace boost::interprocess;
//Typedefs of allocators and containers
typedef managed_shared_memory::segment_manager segment_manager_t;
typedef allocator<void, segment_manager_t> void_allocator;
typedef allocator<int, segment_manager_t> int_allocator;
typedef vector<int, int_allocator> int_vector;
typedef allocator<char, segment_manager_t> char_allocator;
typedef basic_string<char, std::char_traits<char>, char_allocator> char_string;
//Definition of the map holding a string as key and complex_data as mapped type
typedef std::pair<const char_string, int_vector> map_value_type;
typedef std::pair<char_string, int_vector> movable_to_map_value_type;
typedef allocator<map_value_type, segment_manager_t> map_value_type_allocator;
typedef map< char_string, int_vector, std::less<char_string>, map_value_type_allocator> complex_map_type;
shared_memory_object::remove("MySharedMemory");
remove_shared_memory_on_destroy remove_on_destroy("MySharedMemory");
{
//Create shared memory
managed_shared_memory segment(create_only,"MySharedMemory", 65536);
//An allocator convertible to any allocator<T, segment_manager_t> type
void_allocator alloc_inst (segment.get_segment_manager());
//Construct the shared memory map and fill it
complex_map_type *mymap = segment.construct<complex_map_type>
//(object name), (first ctor parameter, second ctor parameter)
("MyMap")(std::less<char_string>(), alloc_inst);
for(int i = 0; i < 100; ++i){
//Both key(string) and value(complex_data) need an allocator in their constructors
char_string key_object(alloc_inst);
int_vector mapped_object(alloc_inst);
mapped_object.push_back(i);
map_value_type value(key_object, mapped_object);
//Modify values and insert them in the map
mymap->insert(value);
}
}
return 0;
}
Try it yourself
I think the problem is that it cannot construct allocators for vectors. You could define an allocator class that has a default ctor which uses mmfile.get_segment_manager()
(then you need to set that through some static data). But a quick fix can be, instead of using the []
operator to add new value, use emplace
.
auto it = mapptr->emplace("Hello", mmfile.get_segment_manager()).first;
it->second.push_back(17);
Sorry, I haven't tested it.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With