ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I know this is a late addition, but the fix I had for this was to have a launch file that specified the env var ROSCONSOLE_CONFIG_FILE for the node that needed to run with debugging
if you had a package my_node
<launch>
<node pkg="my_node" type="first_node" name="first_node"/>
<env name="ROSCONSOLE_CONFIG_FILE" value="$(find my_node)/launch/rosconsole.config"/>
<node pkg="my_node" type="second_node" name="second_node"/>
</launch>
The second node would have the logging enabled for the level you requested in $(rospack find my_node)/launch/rosconsole.config
2 | No.2 Revision |
I know this is a late addition, but the fix I had for this was to have a launch file that specified the env var ROSCONSOLE_CONFIG_FILE for the node that needed to run with debugging
if you had a package my_node
3 | No.3 Revision |
I know this is a late addition, but the fix I had for this was to have a launch file that specified the env var ROSCONSOLE_CONFIG_FILE for the node that needed to run with debugging
if you had a package my_node
my_node
4 | No.4 Revision |
I know this is a late addition, but the fix I had for this was to have a launch file that specified the env var ROSCONSOLE_CONFIG_FILE for the node that needed to run with debugging
if you had a package my_node
<launch>
The second node would have the logging enabled for the level you requested in $(rospack find my_node)/launch/rosconsole.config