Failure in MoveIt! move_group on Ubuntu Mate 16.04 ROS Kinetic on Raspberry Pi 3
Hi everyone,
I am trying to implement and build my manipulator packages on the Raspberry Pi 3, once I have already successfully installed Ubuntu Mate 16.04, ROS Kinetic and MoveIt!, but there are some problems related with the move_group node when I launch my .launch file, although everything worked fine on my Ubuntu 16.04 desktop .
This is what happens when I launch it on the Raspberry Pi 3:
[ INFO] [1500982430.452887547]: Loading robot model 'manipulator'...
...
[move_group-4] process has died [pid 2757, exit code -11, cmd /opt/ros/kinetic/lib/moveit_ros_move_group/move_group --debug __name:=move_group __log:=/home/david/.ros/log/1f22c09e-712d-11e7-8611-7989bb2a9d91/move_group-4.log].
log file: /home/david/.ros/log/1f22c09e-712d-11e7-8611-7989bb2a9d91/move_group-4*.log
I suppose that the problem must be related with the FCL collision libraries of MoveIt! and how they work on Raspberry Pi 3, since if I remove all the visual and collision elements of my URDF file everything works well, but then obviously collisions could not be detected. Anyway, I couldn't figure out how to solve this problem yet, anyone can help me?
Thanks
UPDATE:
This is what I get running the launch file with debug=true
Reading symbols from /opt/ros/kinetic/lib/moveit_ros_move_group/move_group...(no debugging symbols found)...done.
/home/david/1566_embedded_man/embedded_man/rosws/src/manipulator_moveit_config_V3/launch/gdb_settings.gdb: No such file or directory.
Starting program: /opt/ros/kinetic/lib/moveit_ros_move_group/move_group --debug __name:=move_group __log:=/home/david/.ros/log/7e9d1980-7131-11e7-8611-7989bb2a9d91/move_group-4.log
enter code here
[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
Program received signal SIGSEGV, Segmentation fault.
0x76fd9dde in ?? () from /lib/ld-linux-armhf.so.3
(gdb)
as you can see,
gdb
doesn't have any symbols, so it can't give you a proper backtrace.you can try to see what the output is when you enter
bt
and then press the<enter>
key, but I doubt it will be useful.