ros-industrial / ros_qtc_plugin

ROS Qt Creator Plug-in (https://ros-qtc-plugin.readthedocs.io)
396 stars 213 forks source link

Problem to debug ROS2 node in QtCreator #473

Closed jage92 closed 1 year ago

jage92 commented 1 year ago

Hello,

I created a Colcon workspace with a node copied from de tutorials. My QtCreator is in debug mode. When I click run button with the "Run in terminal" checkbox disabled the error is:

>>> [rcutils|error_handling.c:108] rcutils_set_error_state()
This error state is being overwritten:

  'rcutils_expand_user failed, at /tmp/binarydeb/ros-galactic-rcl-logging-interface-2.1.4/src/logging_dir.c:81'

with this new error message:

  'Failed to get logging directory, at /tmp/binarydeb/ros-galactic-rcl-logging-spdlog-2.1.4/src/rcl_logging_spdlog.cpp:84'

rcutils_reset_error() should be called after error handling to avoid this.
<<<
[ERROR] [1669274454.563282727] [rclcpp]: rcl context unexpectedly not shutdown during cleanup
terminate called after throwing an instance of 'rclcpp::exceptions::RCLError'
  what():  failed to configure logging: Failed to get logging directory, at /tmp/binarydeb/ros-galactic-rcl-logging-spdlog-2.1.4/src/rcl_logging_spdlog.cpp:84
08:20:54: /home/jage/ros2_jage_ws/install/xbow400/lib/xbow400/xbow4x_node crashed.

If I activate the "Run in terminal" checkbox, QtCreator freezes and the node not run.

In release mode node runs without problems with and without "Run in terminal" checkbox.

I am using Ubuntu 20, ROS Galactic, QtCreator 8.0.2 and the last version of the QtCreator-ROS installed without SNAP.

EDIT:

Release with Debug information work correctly, with this it is possible to debug the nodes.

EDIT2: The problem was a bad configuration of the workspace and the Clear system environment checkbox activated. This checkbox is in Projects' ->Build->Build environment->Details`

I think that the issue can be closed.