Set a break point to debug in move_group

asked 2020-09-14 09:22:21 -0500

bgraysea gravatar image

updated 2021-04-24 02:34:11 -0500

I'm trying to connect a vs-code debugger into a docker container; which introduces a few areas I could have mistakes in; so I'm gently drifting round in circles unfort. I'm open to any other suggestions on interactive debugging; I'm only using the current stack due to have (limited) experience with it.

I installed debug symbols with apt install ros-melodic-moveit-core-dbgsym and launched my launch file with ... demo.launch debug:=true ... in the console output from there however I see the log message

Reading symbols from /opt/ros/melodic/lib/moveit_ros_move_group/move_group...(no debugging symbols found)...done.

So I'm wondering if I've got something incorrect here already?

Appreciate the below is not Moveit related; just listing for completeness

I do get 2 gdb processes (one for rViz; one for move_group I think/ hope) and I can connect to it from vs-code with some vs-code specific config to connect into the docker container. However; if I click a line to set a break point in vs-code; the debug circle is clear (solid red normally indicates it will break when execution gets there) and I see some output in vs-code

Program received signal SIGINT, Interrupt.
0x00007f368f80bcc4 in ?? ()

If it seems like I'm doing the right steps from moveit side then I'll move the vs-code questions to the appropriate place ... but if I don't have the moveit debug symbols setup correctly; then that may be the first issue I currently have.

edit retag flag offensive close merge delete