[Boost-users] multi_index in managed_shared_memory

Subject: [Boost-users] multi_index in managed_shared_memory
From: Sebastien Nobert (sebastien.nobert_at_[hidden])
Date: 2013-12-10 09:49:31

Hi All,

    I'm trying to build a multi_index in managed shared memory with two (or
more) hashed index but I get an "is an amiguous base of" error. I've
already done that with one hash_uniq and a sequenced index and everything
work fine.

With two hashed index i get.

boost/interprocess/detail/mpl.hpp:74:55: error:
> ‘boost::multi_index::detail::hashed_index_node_impl<boost::interprocess::allocator<char,
> boost::interprocess::segment_manager<char,
> boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family>,
> boost::interprocess::iset_index> > >’ is an ambiguous base of
> ‘boost::multi_index::detail::hashed_index_node<boost::multi_index::detail::hashed_index_node<boost::multi_index::detail::index_node_base<element,
> boost::interprocess::allocator<element,
> boost::interprocess::segment_manager<char,
> boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family>,
> boost::interprocess::iset_index> > > > >’
>     static const bool value = sizeof(dispatch(trigger())) ==
> sizeof(true_t);
>

With a hashed and an ordered index i get.

boost/multi_index_container.hpp:161:52: error: no type named
> ‘final_allocator_type’ in ‘boost::multi_index::multi_index_container< ...
>

and it ask me to attach the preprocessed file to my bug report.

This is compiled on linux with  gcc version 4.8.2 20131017 (Red Hat
4.8.2-1) (GCC)

 Should I open a bug report ? Am I doing something wrong ?

Thanks a lot.

Seb