We have used log4cxx V0_10_0 since a few years with both Linux and Windows without any issues until now. We have a setup to compile and build the log4cxx shared library on both Linux and Window. We made a solution (sln) that can build with Microsoft VS 2008 up to VS 2013. Our log4cxx is build under gentoo for Linux. 

We recently started to have a crash with a testing application under Linux Gentoo when a testing application exit and the destruction of the static singletons of the log4cxx library proceed. However the same testing application doesn't crash under Windows with VS 2013. We would appreciate at any hints that could help us fix the crash issue under Linux. The stack of the crash is:

#0  0x00007f2cde67d805 in ?? () from /lib64/libc.so.6
#1  0x00007f2cde67e878 in ?? () from /lib64/libc.so.6
#2  0x00007f2ce7b829b3 in std::_Rb_tree<std::string, std::pair<std::string const, log4cxx::helpers::ObjectPtrT<log4cxx::Logger> >, std::_Select1st<std::pair<std::string const, log4cxx::helpers::ObjectPtrT<log4cxx::Logger> > >, std::less<std::string>, std::allocator<std::pair<std::string const, log4cxx::helpers::ObjectPtrT<log4cxx::Logger> > > >::_M_erase(std::_Rb_tree_node<std::pair<std::string const, log4cxx::helpers::ObjectPtrT<log4cxx::Logger> > >*) () from /usr/lib64/liblog4cxx.so.10
#3  0x00007f2ce7b80940 in log4cxx::Hierarchy::~Hierarchy() () from /usr/lib64/liblog4cxx.so.10
#4  0x00007f2ce7b80b99 in log4cxx::Hierarchy::~Hierarchy() () from /usr/lib64/liblog4cxx.so.10
#5  0x00007f2ce7b98c46 in log4cxx::spi::DefaultRepositorySelector::~DefaultRepositorySelector() () from /usr/lib64/liblog4cxx.so.10
#6  0x00007f2ce7b989c0 in log4cxx::helpers::ObjectPtrT<log4cxx::spi::RepositorySelector>::~ObjectPtrT() () from /usr/lib64/liblog4cxx.so.10
#7  0x00007f2cde63beef in __cxa_finalize () from /lib64/libc.so.6
#8  0x00007f2ce7b4ab33 in ?? () from /usr/lib64/liblog4cxx.so.10​


Guy Bonneau