`roslaunch pr2_moveit_config demo.launch` fails
I'm trying to run Dave Coleman's demo which I cloned from his repo: https://github.com/davetcoleman/pr2_m... .
This works fine:
roslaunch moveit_setup_assistant setup_assistant.launch
However, I've troubles with the following:
roslaunch pr2_moveit_config demo.launch
When I run this line, lots of things happen, then RViz starts and after a short while fails, leaving this message in terminal:
[rviz_c8d753b8ad42_15266_8281796835458697607-6] process has died [pid 15335, exit code -11, cmd /opt/ros/kinetic/lib/rviz/rviz -d /root/ws_moveit/install/share/pr2_moveit_config/launch/moveit.rviz __name:=rviz_c8d753b8ad42_15266_8281796835458697607 __log:=/root/.ros/log/af9613b0-f21b-11e6-b13f-0242ac110002/rviz_c8d753b8ad42_15266_8281796835458697607-6.log].
log file: /root/.ros/log/af9613b0-f21b-11e6-b13f-0242ac110002/rviz_c8d753b8ad42_15266_8281796835458697607-6*.log
Unfortunately, there's no logfile from RViz, only master.log, rosout.log etc., none of which provides any valuable info. Does anyone know where this error might come from? How to troubleshoot, where do I start? How to make rviz output logs at least?
I'm running it from a docker container, if it matters.
Thanks in advance.
No problems with
roscore &; rviz, by the way.You could see whether running RViz in gdb and printing a backtrace provides any useful information. For that to really help you'd need debug symbols for RViz.
re: logging: rviz crashes before it can write anything to the logs.
@gvdhoorn Thanks for the suggestion, but it works fine when I run RViz just from a command line. Any ideas on how to run it in gdb while executing
roslaunch pr2_moveit_config demo.launch? My guess is I have to mess withdemo.launchfile, right? Or, build RViz from scratch with debug symbols?re: debug symbols: yes, that will unfortunately require a from-source build.
re: running rviz in gdb:
demo.launchalready includes support for that. Just run it asdemo.launch debug:=true.@gvdhoorn That's nice. Good, unless someone has a solution or I magically resolve it myself, I'll give gdb a try. Thank you.
@gvdhoorn Well, as usual, the problem turned out to be absolutely dumb. I suspected that, just didn't expect it to be SO dumb. Anyway, thanks for your comments, might come in handy at some point later.