Opened 9 years ago
Closed 9 years ago
#9064 closed Bugs (fixed)
select_on_container_copy_construction for scoped_allocator segfaults
Reported by: | Owned by: | Ion Gaztañaga | |
---|---|---|---|
Milestone: | To Be Determined | Component: | container |
Version: | Boost 1.54.0 | Severity: | Regression |
Keywords: | Cc: |
Description
using gcc 4.4.7 or 4.6.3 for linux the following code segfaults due to a problem with select_on_container_copy_construction
#include <memory> #include <boost/container/scoped_allocator.hpp> #include <boost/container/vector.hpp> int main(int argc, char* argv[]) { typedef boost::container::scoped_allocator_adaptor<std::allocator<int> > Allocator; typedef boost::container::vector<int, Allocator> MyVector; MyVector test1; MyVector test2(test1); };
Attachments (1)
Change History (5)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
The inner_traits_type::select_on_container_copy_construction(this->inner_allocator()) statement in select_on_container_copy_construction causes an infinite recursion loop for a scoped allocator without any inner allocator type. (Inner allocator points back to outer) Somehow one has to distinguish the cases without and with inner allocator. In the latter case skipping the inner_traits_type::select_on_container_copy_construction part in the constructor call could be used to break the loop.
by , 9 years ago
Attachment: | select_on_conatiner_copy.patch added |
---|
comment:3 by , 9 years ago
Thanks for the report and the patch. I've modified it to pass the logic to the bass class, where an specialization for 0 inner alllocator can handle select_on_container_copy_construction a bit differently.
The same code runs fine with boost 1.52.0