Skip to content
This repository has been archived by the owner on Nov 13, 2017. It is now read-only.
This repository has been archived by the owner on Nov 13, 2017. It is now read-only.

Segfault while launching moveit_setup_assistant on jade-devel on ROS Kinetic #119

Closed

Description

Launching moveit_setup_assistant using the following command as documented on ROS Kinetic yields a segmentation fault.

roslaunch moveit_setup_assistant setup_assistant.launch

outputs:

SUMMARY
========

PARAMETERS
 * /rosdistro: kinetic
 * /rosversion: 1.12.2

NODES
  /
    moveit_setup_assistant (moveit_setup_assistant/moveit_setup_assistant)

auto-starting new master
process[master]: started with pid [17777]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to ed290684-5319-11e6-b625-0242ac110002
process[rosout-1]: started with pid [17790]
started core service [/rosout]
process[moveit_setup_assistant-2]: started with pid [17802]
================================================================================REQUIRED process [moveit_setup_assistant-2] has died!
process has died [pid 17802, exit code -11, cmd /root/ws_moveit/devel/lib/moveit_setup_assistant/moveit_setup_assistant __name:=moveit_setup_assistant __log:=/root/.ros/log/ed290684-5319-11e6-b625-0242ac110002/moveit_setup_assistant-2.log].
log file: /root/.ros/log/ed290684-5319-11e6-b625-0242ac110002/moveit_setup_assistant-2*.log
Initiating shutdown!
================================================================================
[moveit_setup_assistant-2] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

There is no such file as /root/.ros/log/ed290684-5319-11e6-b625-0242ac110002/moveit*.

I've built MoveIt myself from the experimental unified repository.

I've tried to add a breakpoint on the entry of the main function in setup_assistant_main.cpp using CLion [I'm not familiar with gdb] - and it does not even get hit.
moveit_setup_assistant_segfault

Here is the full text under visible within the Thread-1 window:

long double boost::math::detail::erf_imp<long double, boost::math::policies::policy<boost::math::policies::promote_float<false>, boost::math::policies::promote_double<false>, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy> >(long double, bool, boost::math::policies::policy<boost::math::policies::promote_float<false>, boost::math::policies::promote_double<false>, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy, boost::math::policies::default_policy> const&, mpl_::int_<64> const&)

I've googled a bit, and found that such Boost errors might be caused by different versions or flags of the compiler. I've first tried to build MoveIt with clang, which failed, and then tried to use the already-built from sources moveit-kinetic-source Docker image. Even on that image, I'm getting the same segmentation fault upon the start of the moveit_setup_assistant node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions