【发布时间】:2014-11-11 23:40:46
【问题描述】:
我对侵入式容器的理解有了很大进步。我有一个运行“一段时间”的程序,然后在这样的代码行上删除 *it; (见下文):
....
// : public list_base_hook< void_pointer< ip::offset_ptr<void> > >
class OneDepthPrice : public list_base_hook<link_mode<auto_unlink>> // This is a derivation hook
{
public:
Provider provider;
Price price;
public:
list_member_hook<link_mode<auto_unlink>> member_hook_; // This is a member hook
OneDepthPrice(Provider prov, Price p) : provider(prov), price(p) {}
};
...
std::vector<OneDepthPrice *>& vecPrices
for (auto it = vecPrices.begin(); it != vecPrices.end(); ++it)
{
auto& e = *it;
#if DEBUG
std::cout << e->provider.name << "\n" << std::flush;
#endif
if(e->provider.name == newPrices.provider.name)
{
delete *it; //This is the offending line in the stack trace in the debugger.
it = vecPrices.erase(it);
}
}
程序因堆栈跟踪而崩溃:
#0 0x407ddd boost::intrusive::list_node_traits<void*>::set_next(n=@0x7fffffffe2b8: 0x0,
next=@0x7fffffffe2b0: 0x706860) (/usr/local/include/boost/intrusive/detail/list_node.hpp:64)
#1 0x409189 boost::intrusive::circular_list_algorithms<boost::intrusive::list_node_traits<void*> >::unlink(this_node=@0x7fffffffe2e8: 0x706830) (/usr/local/include/boost/intrusive/circular_list_algorithms.hpp:140)
#2 0x407e2a boost::intrusive::generic_hook<boost::intrusive::get_list_node_algo<void*>, boost::intrusive::default_tag, (boost::intrusive::link_mode_type)2, (boost::intrusive::base_hook_type)1>::unlink(this=0x706830) (/usr/local/include/boost/intrusive/detail/generic_hook.hpp:180)
#3 0x406b5c boost::intrusive::detail::destructor_impl<boost::intrusive::generic_hook<boost::intrusive::get_list_node_algo<void*>, boost::intrusive::default_tag, (boost::intrusive::link_mode_type)2, (boost::intrusive::base_hook_type)1> >(hook=...) (/usr/local/include/boost/intrusive/detail/utilities.hpp:371)
#4 0x405b13 boost::intrusive::generic_hook<boost::intrusive::get_list_node_algo<void*>, boost::intrusive::default_tag, (boost::intrusive::link_mode_type)2, (boost::intrusive::base_hook_type)1>::~generic_hook(this=0x706830, __in_chrg=<optimized out>) (/usr/local/include/boost/intrusive/detail/generic_hook.hpp:160)
#5 0x40534a boost::intrusive::list_base_hook<boost::intrusive::link_mode<(boost::intrusive::link_mode_type)2>, void, void>::~list_base_hook(this=0x706830, __in_chrg=<optimized out>) (/usr/local/include/boost/intrusive/list_hook.hpp:86)
#6 0x405546 OneDepthPrice::~OneDepthPrice(this=0x706830, __in_chrg=<optimized out>) (/home/idf/Documents/TestCPPArrays/TestCPPArrays.cpp:86)
#7 0x403728 UpdateBunchTogether(vectogether=..., vecPrices=..., newPrices=...) (/home/idf/Documents/TestCPPArrays/TestCPPArrays.cpp:291)
#8 0x404765 main() (/home/idf/Documents/TestCPPArrays/TestCPPArrays.cpp:558)
这是一个奇怪的错误,因为该程序不是多线程的,但它可以顺利运行一段时间。我不确定发生了什么,但也许我需要使用 smart_pointers?
【问题讨论】:
-
问题:为什么要使用侵入式容器?如果您要存储指针,那么一定要使用常规容器。
-
sehe,最大的原因是我喜欢 IC,即不必担心对象存储/引用的所有不同位置的语义。我只是从一个地方删除它,所有其他地方都会自动更新。
-
我会这么说,我很可能能够使用常规对象而不是指针。我只是看不到让它发挥作用。
-
那么您确实需要 shared_pointers 或享元(启用跟踪)。您不想仅仅为此使用侵入式容器,因为您会陷入生命周期管理的混乱之中。
-
好的,您在 IC Q1 中的建议使我得到了这个解决方案。我还看到它们的性能非常高,这是非常可取的。我会研究你的其他建议。你是说sp+ics吗? sps 没有 ic 整洁的功能,我只需要担心删除它们的地方吗?不知道什么是蝇量级...
标签: c++ c++11 boost std intrusive-containers