Open wxmerkt opened 5 years ago
I am getting a similar segmentation fault between a BVH and a primitive (box) - possibly a separate issue?:
#0 0x00007fffa1dec502 in fcl::detail::GJKSolver_libccd<double>::S fcl::distance<fcl::detail::GJKSolver_libccd<double> >(fcl::CollisionGeometry<fcl::detail::GJKSolver_libccd<double>::S> const*, Eigen::Transform<fcl::detail::GJKSolver_libccd<double>::S, 3, 1, 0> const&, fcl::CollisionGeometry<fcl::detail::GJKSolver_libccd<double>::S> const*, Eigen::Transform<fcl::detail::GJKSolver_libccd<double>::S, 3, 1, 0> const&, fcl::detail::GJKSolver_libccd<double> const*, fcl::DistanceRequest<fcl::detail::GJKSolver_libccd<double>::S> const&, fcl::DistanceResult<fcl::detail::GJKSolver_libccd<double>::S>&) () from [path]/libfcl.so.0.6
#1 0x00007fffa1dec815 in double fcl::distance<double>(fcl::CollisionObject<double> const*, fcl::CollisionObject<double> const*, fcl::DistanceRequest<double> const&, fcl::DistanceResult<double>&) () from [path]/libfcl.so.0.6
Using the latest master (2112037d3f0490f83c9e2d237886eb113b7b0d31), I get the following kind of segmentation faults fairly often (it's also happening with older commits):
I.e., when computing a distance between a Box and a Cylinder using libccd's GJK. Alas, I do not have a reproduction case. Have you seen these kind of segmentation faults?
I am on Ubuntu 18.04, using the latest libccd and FCL (2112037d3f0490f83c9e2d237886eb113b7b0d31). Compiled without SSE or march=native.