[Quickfix-developers] QuickFix 1.12.4 message_order assigment crash
Brought to you by:
orenmnero
|
From: Alexander L. <Ale...@so...> - 2006-11-20 16:20:01
|
Hello Everyone, I'm having an issue with message_order on a client I recently ugraded to 1.12.4. All works fine but after update i got 2 response from clients with next crash: WARNING: Stack unwind information not available. Following frames may be wrong. kernel32!RaiseException+0x52 vktt!_CxxThrowException+0x46 vktt!operator new+0x69 vktt!FIX::message_order::operator=+0x44 vktt!std::_Tmap_traits<int,FIX::FieldBase,FIX::message_order,std::allocator<std::pair<int const ,FIX::FieldBase> >,1>::_Tmap_traits<int,FIX::FieldBase,FIX::message_order,std::allocator<std::pair<int const ,FIX::FieldBase> >,1>+0x42 vktt!std::_Tree<std::_Tmap_traits<int,FIX::FieldBase,FIX::message_order,std::allocator<std::pair<int const ,FIX::FieldBase> >,1> >::_Tree<std::_Tmap_traits<int,FIX::FieldBase,FIX::message_order,std::allocator<std::pair<int const ,FIX::FieldBase> >,1> >+0x49 vktt!FIX::FieldMap::FieldMap+0x37 vktt!FIX::FieldMap::addGroup+0x7c vktt!FIX::Message::setGroup+0x280 vktt!_fpclass+0xe84d MSWSOCK+0x44b0 Unfortunately i dont know type of exception. Seems that copied message_order object has negative member m_largest. Maybe someone have any idea? Thanks, Sasha |