Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

Ok, I managed to track down the problem. OMPL (and planning environment I guess) requires the default_collision_operations parameter to be set. It simply gives a warning when it doesn't find it, but a huge chunk a code doesn't get run and it triggers a SEGFAULT a long time later!

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.