ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

No DEBUG messages on stdout/stderr

asked 2022-08-28 21:30:35 -0500

joaocandre gravatar image

updated 2022-08-28 21:30:58 -0500

When printing/logging messages with ROS_DEBUG there is no output on stdout/stderr, despite launching a node with output="screen". On the other hand, ROS_INFO, ROS_WARN and ROS_ERROR (along with their variants) work as intended, printing the message to the console.

Looking into ROS logging documentation, debug messages should be printed by default, while warning and error message shouldn't. In additions, nothing is printed to logfiles.

How do I go about fixing this?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2022-08-28 23:50:54 -0500

gvdhoorn gravatar image

updated 2022-08-28 23:56:46 -0500

debug messages should be printed by default, while warning and error message shouldn't.

could you clarify what makes you conclude this? Preferably using a quote from the page you link?

The Output section mentions that everything only ends up on stdout and stderr "if they are enabled" (the log levels that is, not stdout or stderr).

The default log level is INFO, not DEBUG (end of the Log Statements section):

The default verbosity level is INFO, so DEBUG statements will not be seen by default.

For DEBUG messages to be logged, you'll have to change the debug level of the logger that's emitting them. You could do that using a .conf file loaded by your .launch (wiki/rosconsole: Configuration).

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2022-08-28 21:30:35 -0500

Seen: 378 times

Last updated: Aug 28 '22