#23 0x00007ffff7bc0b30 in CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::_cxx11::basic_string, std::allocator > const&) () from /usr/lib/x86_64-linux-gnu/libcppunit-1.13.so.0

#22 0x00007ffff7bb84c2 in CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) () #21 0x00007ffff7bb1b93 in CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) ()Р”Р‡rom /usr/lib/x86_64-linux-gnu/libcppunit-1.13.so.0 #16 0x00007ffff71c60fb in PyRun_SimpleStringFlags (command=0x4dcd30 'builtins.props = prop_tree.Props(new_tree=False)', flags=0x0) #15 PyRun_StringFlags 'builtins.props = prop_tree.Props(new_tree=False)', globals=0x7a4868, #10 PyEval_EvalFrameEx at Python/ceval.c:3236 #9 call_function (oparg=, pp_stack=0x7fffffffc0b0) at Python/ceval.c:4732 #3 0x00007ffff64f289c in _GI_fortify_fail (msg=, 'stack smashing detected') at fortify_fail.c:37 Could you check if this now works?Р”В®dit2: Note that the gdb backtrace is much more informative if you compile your own Python version as described earlier:Р”В¬ode: Select all #0 0x00007ffff640f418 in _GI_raise at. I tracked this down to a bug in Python itself - in the PyArg_ParseTupleAndKeywords() function where the 'p' argument format is not correctly converted into a C bool type, and fixed it in the python/r9 branch. I also see the smashed stack issue when I compile my own Python-3.5.2 version (edit: in my Ubuntu 16.04 VM).

Mpi stack smashing detected c++