Pablo Garrido

Could you share the whole demo code to replicate it?

Are you using the [micro_ros_espidf_component](https://github.com/micro-ROS/micro_ros_espidf_component)? Make sure that you are building the library with enough static memory allocations: https://github.com/micro-ROS/micro_ros_espidf_component/blob/dac6f808f059e40a11d9e210ff20512a106474ac/colcon.meta#L39 --- If you are using [micro_ros_setup](https://github.com/micro-ROS/micro_ros_setup) check your [app-colcon.meta](https://github.com/micro-ROS/freertos_apps/blob/foxy/apps/int32_publisher/app-colcon.meta)

Please detail which build system are you using and detail the process of rebuilding because in some cases you need to clean some files to have a complete rebuild.

Ok, I have not replicated the issue but I have seen that the `rcl_interfaces__msg__Log` has these members: ```c typedef struct rcl_interfaces__msg__Log { builtin_interfaces__msg__Time stamp; uint8_t level; rosidl_runtime_c__String name; rosidl_runtime_c__String msg;...

I think that we should think about integrating this along the rclc/rcl in order to get a logging interface like ROS 2. Which user API will you expect to have...

> Now that some time has passed: @pablogs9: would https://github.com/ros2/rclc/issues/55#issuecomment-790354834 still be the best/most straightforward way for a micro-ROS application to log to rosout? That's it

> None of the functionality in rcutils can be used? I should recheck this, but if I remember well, most of the logging functionality is removed in micro-ROS's rcutils due...

> IIUC, you're mostly referring to [these changes to `error_handling.h`](https://github.com/micro-ROS/rcutils/commit/b1997d8d099475398c5d9e4d80fa9b8650c9b42b#diff-2b6584cb7cab0699df7fab74d45c78dab24ac9d40a89dd1c84d0a7e35e6f13d3), correct? yes

@JanStaschulat any idea?

Related https://github.com/micro-ROS/micro-ROS-demos/issues/56