ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
5

Error using ros::shutdown and moveit

asked 2014-05-05 01:46:06 -0600

paturdc gravatar image

I read somewhere that this is a fairly benign error, but does anyone know why ROS doesn't shut down correctly when using moveit? I get the following error message:

move_joint_goal: /usr/include/boost/thread/pthread/pthread_mutex_scoped_lock.hpp:26: boost::pthread::pthread_mutex_scoped_lock::pthread_mutex_scoped_lock(pthread_mutex_t*): Assertion `!pthread_mutex_lock(m)' failed. Aborted (core dumped)

Everything works fine until then, I can move my robot, and get state information and all.

edit retag flag offensive close merge delete

Comments

Good question, I always get the same error. I guess nobody cares because it only happens on shutdown, but it bugs me too. Maybe ask this question over at the MoveIt Google groups mailing list, that's where the MoveIt developers are.

Martin Günther gravatar image Martin Günther  ( 2014-05-05 22:39:25 -0600 )edit

It's a bit weird when you're just starting, and I get my own segmentation faults, and I can't work out what is wrong with my own application. But since it is apparently not very important, I'm just leaving it.

paturdc gravatar image paturdc  ( 2014-05-06 07:58:38 -0600 )edit

2 Answers

Sort by » oldest newest most voted
0

answered 2014-07-29 10:09:55 -0600

Maestre gravatar image

Hi! I am just having the same problem in CPP when using MoveGroup (for example, moveit::planning_interface::MoveGroup group("right_arm"));

As this makes my program to be killed when exiting I cannot use Valgrind to seek for memory leaks. Any solutions?

edit flag offensive delete link more

Comments

Please do not post your question in an answer section (to the worst, your additional question wouldn't get as much attention by doing so).

130s gravatar image 130s  ( 2018-09-19 14:29:18 -0600 )edit
0

answered 2018-09-19 14:33:14 -0600

130s gravatar image

A ticket with the same error message was closed a while ago, so I hope it's safe to assume it's resolved (if not please add comments in the referenced ticket).

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2014-05-05 01:46:06 -0600

Seen: 938 times

Last updated: Sep 19 '18