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.

ROS2 managed Python node: exception stacktrace is not logged

asked 2023-07-19 05:41:09 -0500

LastStarDust

3 ●2 ●4 ●6

updated 2023-07-19 05:41:45 -0500

In managed lifecycle Python nodes, if an exception happens during a transition, the stack trace is not logged. Is this a bug or a feature? If It is a feature, how do I enable the logging?

In CPP nodes, the stack trace is logged by default.

PS One month ago, I asked a related question here but it is still unanswered.

edit retag flag offensive close merge delete

add a comment

Question Tools

1 follower

Stats

Asked: 2023-07-19 05:41:09 -0500

Seen: 58 times

Last updated: Jul 19 '23

ROS2 managed Python node: exception stacktrace is not logged edit

Question Tools

Stats

Related questions

ROS2 managed Python node: exception stacktrace is not logged