Python Unittests segfaulting
On MacOS and Linux the unittests for the python bindings will segfault occasionally.
This also happens for boost versions > 1.55 (and for all possible combinations of compilers and c++ standards see here).
So far this has only happend for release builds and not debug builds, which might imply that there is a problem with uninitialized variables.
Cppcheck seems to be very happy with the bindings code.
Half of the builds fail because of actual build errors (and not segfaulting unittests).
The build errors are caused by passing -DSTL_VECTOR_CHECKS=ON to cmake, which enables GLIBCXXDEBUG.
We can get rid of these errors by either disabling STL_VECTOR_CHECKS or using a GLIBCXX_DEBUG enabled version of boost. The latter can be build using $ bjam define=GLIBCXX_DEBUG.
The builds for the python unittests should now build with disabled vector checks.
Milestone changed to OpenMesh 6.0Toggle commit list
Milestone removedToggle commit list