Re: Ignite 2.0 C++ Segfault

2017-05-12 Thread Igor Sapego
Hi, Thanks for the report - I'll investigate the issue and let you know. We do not use std::shared_ptr as we want to let C++03 applications use Ignite too. Best Regards, Igor On Fri, May 12, 2017 at 11:56 AM, tolga wrote: > There seems to be some kind of race situation: > 0x01381206 in

Re: Ignite 2.0 C++ Segfault

2017-05-12 Thread tolga
There seems to be some kind of race situation: 0x01381206 in std::less::operator() (this=0x1a4e4b0, __x=, __y=@0x7fff80846e04: 2066246303) at /usr/include/c++/6.3.1/bits/stl_function.h:386 #4 0x015040cd in ignite::impl::binary::BinaryTypeManager::GetHandler (this=0x1a560d0, typeNam

Ignite 2.0 C++ Segfault

2017-05-12 Thread Tolga HOŞGÖR
The following segfault happens in multi-threaded ignite c++ application: C [test+0xf8116a] std::less::operator()(int const&, int const&) const+0x14 C [test+0x1106305] std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::_M_lower_bound(std::_Rb_tree_node > >*, std::_Rb_tree_no