id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
11912,boost::interprocess::flat_map use of vector::priv_forward_range_insert_expand_backwards may cause boost::container::move with same source and destination,zeeshan.qazi@…,Ion Gaztañaga,"boost::interprocess::flat_map use of vector::priv_forward_range_insert_expand_backwards may cause boost::container::move with same source and destination.

If an allocator that supports expand_backwards or expand_forwards is used and either of the operation succeeds with the capacity of  increasing by the count of elements being inserted, and the elements being inserted happen to be placed in the direction of the expansion, then the following line (marked:>>>>) in vector.hpp computes the raw_gap as zero:

            //Old situation:
            // __________________________________________________
            //|            raw_mem         | old_begin | old_end |
            //| ___________________________|___________|_________|
            //
            //New situation:
            // __________________________________________________
            //| old_begin |   new    | old_end |  raw_mem        |
            //|___________|__________|_________|_________________|
            //
            //Now initialize the rest of memory with the last old values
            //All new elements correctly constructed, avoid new element destruction
>>>>            '''const size_type raw_gap = s_before - before_plus_new;'''
            if(!value_traits::trivial_dctr){

This results in boost::container::move being called with the same source and destination.",Bugs,closed,To Be Determined,interprocess,Boost 1.61.0,Problem,fixed,,