Re: [Boost-users] Correct way to store shared_ptr objects in a stl::map

Ovanes Markarian wrote:

I had some similar issue but not with shared_ptr. My problem was the redefinition for debug purposes (to make mem allocation statistics) of the global new operator. In this case the default allocator used the rewritten new operator to allocate container storage and the rewritten operator used the std::allocator and this cycle caused the behaviour. Is there any chance that this might be the cause?

Not likely, ::operator new in sp_debug_hooks just uses malloc to allocate memory and then marks it with a magic value for tracking purposes.