Problem with ros_control and gazebo

edit

@msaws You say you have tried this and this tutorial which expain you how to deal with URDF, ROS_control and Gazebo? It is strange that this does not work... Are you able to post your description and configuration files? With the information you gave it seems that the Controllers are not properly loaded in ROS_control, maybe you gave a wrong joint name or your configuration file is not properly written. Besides I recommend you to work on a proper namespace and not over the global /.

@Weasfas I checked the joint names, I don't think the problem is with controllers not loading because I even tried to with roslaunch rrbot_gazebo rrbot_world.launch it gives me same error. I think the problem is with gazebo_ros_control plugin I'm not sure I couldn't figure out the problem

I do not think it is a problem of gazebo_ros_control, you are getting a segmentation fault expection. If the problem was in ROS control it should warn yourself of the controllers not loading, and it does not even reach that part. Ensure you have all dependencies installed and your URDF and world are correct. In the past I have experienced the same issue when I load a wrong URDF or the .world file was bad formatted.

Furthermore the plugin needs several parameters like:

<gazebo>
    <plugin name="gazebo_ros_control" filename="libgazebo_ros_control.so">
        <robotNamespace>/your_namespace</robotNamespace>
        <robotParam>your_robot_description</robotParam>
        <controlPeriod>0.001</controlPeriod>
        <robotSimType>gazebo_ros_control/DefaultRobotHWSim</robotSimType>
        <legacyModeNS>true</legacyModeNS>
    </plugin>
</gazebo>

I changed my plugin to

<gazebo>
    <plugin name="gazebo_ros_control" filename="libgazebo_ros_control.so">
        <robotNamespace>/myrobot</robotNamespace>
        <robotSimType>gazebo_ros_control/DefaultRobotHWSim</robotSimType>
        <robotParam>/myrobot/robot_description</robotParam>
        <legacyModeNS>true</legacyModeNS>
    </plugin>
</gazebo>

it gave me

[ INFO] [1597769945.328490084]: Starting gazebo_ros_control plugin in namespace: /myrobot
[ INFO] [1597769945.329537727]: gazebo_ros_control plugin is waiting for model URDF in parameter [/myrobot/robot_description] on the ROS param server.
[urdf_spawner-4] process has finished cleanly

I hope this correct but when I launch my controller

[INFO] [1597769968.108590]: Controller Spawner: Waiting for service controller_manager/load_controller
[WARN] [1597769998.349820]: Controller Spawner couldn't find the expected controller_manager ROS interface.
[myrobot/controller_spawner-1] process has finishe

And what all dependencies should I install?

You need to load your robot_description in the proper namespace and I was refering to the dependencies from gazebo_ros_control, gazebo_ros_plugins, and each dependency package regarding the controllers you are using: joint_position, joint_effort etc. It will be easier if you post the launch files or something to debug what is happening.

@Weasfas I've updated the question and added my urdf and controller, I don't know why but I couldn't add more so I'm adding my launch files here in comments

controller launch file:

<launch>
  <rosparam file="$(find myrobot)/config/arm_controller.yaml" command="load"/>

  <node name="controller_spawner" pkg="controller_manager" type="spawner" respawn="false"
    output="screen" ns="/myrobot" args="joint_state_controller
                      joint1_position_controller
                      joint2_position_controller
                                          joint3_position_controller
                      joint4_position_controller
                                          joint5_position_controller
                      joint6_position_controller
                                          joint7_position_controller
                      joint8_position_controller"/>

  <node name="robot_state_publisher" pkg="robot_state_publisher" type="robot_state_publisher"
    respawn="false" output="screen">
    <remap from="/joint_states" to="/myrobot/joint_states" />
  </node>

</launch>