Re: RFC: Stopping Zephyr networking from being painful by enabling error logging by default


Boie, Andrew P
 

My views on this topic:

1) Right now we have very inconsistent error/debug logging. In lots of places in the kernel, when a bad situation is encountered the problem is simply reported with a printk(). In other places we are using SYS_LOG_*. The default experience for the user is that all the SYS_LOG messages are suppressed, but the printks are emitted. This is not an ideal default configuration, in fact words like "horrible" and "baffling" come to mind when considering it.

2) I still think that SYS_LOG should be turned on by default for error and warning situations, just like printk() is on by default.

3) If people are concerned about code size, there should be some kind of global flag which suppresses all debug output, including printk(). In the future, for very RAM constrained devices we could implement a backend to SYS_LOG which uses tricks like storing format strings completely outside the binary, in an external file used to decode raw log data, stuff like that.

4) The way SYS_LOG_* is configured in Kconfig is currently a confusing disaster and I look forward to seeing what Paul comes up with to clean it up. I think the difficulty in using this mechanism is at least partly why large parts of the kernel do not use it and just do printks instead.

5) We may consider making printk() a thin wrapper for a particular level of SYS_LOG().

Andrew

Join devel@lists.zephyrproject.org to automatically receive all group messages.