Boost 1.55.0 beta1: circular_buffer incompatible with shared memory allocators?

[Dr Leonid Timochouk <L.Timochouk@…>]

Apparently, because of the use of "placement new" instead of "m_alloc.construct()" used in previous versions, Circular Buffer can no longer be used with allocators which return a pointer type different from void*. In particular, shared memory allocators provided by the Interprocess library result in a compile-time error. This seems to be a serious regression.

[anonymous]

I am afraid that this bug has now been hidden away from view because of the owner change, and no Cc: added.

This isssue is making it impossible for me to use the circular_buffer from 1.55.

[Jan Gaspar]

Sorry about this, but I'm not maintaining circular_buffer any more.

[saleyn@…]

Patch that fixes reported issue with circular buffer

[saleyn@…]

Who is in charge of maintaining this project, can we get this fix applied to to the new release?

[Jan Gaspar]

Sure, you can fix the issue and also you can start maintaining the library if you wish.

[Serge Aleynikov <saleyn@…>]

Replying to jano_gaspar:

Sure, you can fix the issue and also you can start maintaining the library if you wish.

Do you mind pushing this fix into the release area? Aside from fixing this issue, unfortunately, I have no resources to be able to become the maintainer of this project.

[Jan Gaspar]

You need to ask someone at boost dev mailing list to push it for you I'm afraid.

[Antony Polukhin]

This issue is not as easy as it looks like:

• Replacing placement new with allocator's construct() breaks move emulation under C++03, where construct accepts parameter by const reference, while Boost.Move requires nonconst reference.

• Older versions of circular buffer did not work well in DEBUG mode: std::memset was attempting to convert typename Allocator::pointer to void*.

Attached a patch that fixes the issue. Will be applied as soon as the GIT migration will be finished.

[Antony Polukhin]

More advanced patch, based on the previous one.

[Serge Aleynikov <saleyn@…>]

Thanks for looking into it!

Replying to apolukhin:

This issue is not as easy as it looks like:

• Replacing placement new with allocator's construct() breaks move emulation under C++03, where construct accepts parameter by const reference, while Boost.Move requires nonconst reference.

• Older versions of circular buffer did not work well in DEBUG mode: std::memset was attempting to convert typename Allocator::pointer to void*.

Attached a patch that fixes the issue. Will be applied as soon as the GIT migration will be finished.

[Antony Polukhin]

In ​commit1 and ​commit2 to GIT's developer branch this issue was addressed.

[Antony Polukhin]

​Fix merged to master branch