• ROS

  • Can't debug c++ module in vscode ROS extention on Ubuntu 18.04.

Hello Team. Needs help with debugging c++ module (from several pakets) in vscode ROS extention (on Ubuntu 18.04). I had rebild some pakets in debug configuration. But breakpoints in sourse code can not been hit. And source code of functions (in callstack window) are not availabled. How this problem will might be solve? Thanks

    jakaskerl

    Thanks for replying.

    I would like to gebug c++ visual odometry system in vscode ROS extention.

    I had been used flag -DCMAKE_BUILD_TYPE=Debug to rebuild shared objects , that had symbols inside.

    But breakpoints does not hit.

    As you can see function is grey in call stack.

    I can pause implementation by call stack but can't stop implementation on breakpoints.

    Could someone give me a tip?

      Hi @ostepan2006, I think this question should be sent to the authors of VSCode ROS extension, unless you are also trying to debug the depthai-ros nodes. Nevertheless, some quick questions:

      1. Which launch file are you trying to debug?
      2. Could you share your config file containing debug launch description?
      3. I see that you are using ROS Melodic which is unfortunately EOL and not supported anymore so I suspect this might also create some issues, would it be possible to try that with ROS Noetic?
      4. If there is a bug in the extension that prevents debugging, you can try debugging without it by running gdb in ROS launch files directly, more information can be found here

        Luxonis-Adam Thanks for replying.

        I had been trying VO system (uzh-rpg/rpg_svo_pro_open) in order to do then 3d reconstruction by images of mono camera (OAK-1). The VO system woks on ROS Melodic. I had been using video tutorial from YouTube "Visual Studio Code ROS Extension" to do vscode settings (c_cppproperties.json, launch.json,settings.json, tasks.json). I had been run catkin make -DCMAKE_BUILD_TYPE=Debug command before start debugging. But my breakpoints is notworking and have gray color (see picture below)

        For debugging I had been using SVO launch file from repository.

        What do you mean by "debug launch description" ? I might share any from setting file.

        As I know gdb has not IDE so is less convenient as vscode.

        Thanks

          Hi, it seems that the configuration is good, so this issue could be caused by the VSCode extension. I'm not sure if ROS Melodic distribution is supported by the authors, maybe you could try running it on Noetic?

            Luxonis-Adam Thanks

            I had been posted a bug about the issue (ms-iot/vscode-ros/) a week ago but nothing activity so far.

            Why do you think Noetic will be better? Actually VO system had been mentonied above was tested on the Melodic.

              Melodic distribution is EOL, which means it's not supported anymore by the creators, which could be the reason for problems with VSCode extension. Noetic distribution is still supported (until 2025), so to get the latest fixes you should use it.