6575e84002
Currently, if CONFIG_LOG_PROCESS_THREAD is enabled, log processing does not start until just before the main() function is called in the user sample. This means that no real-time logging information will be sent to the backends while drivers and/or other processes which are triggered during kernel boot are processing their tasks. Worse, if they take a longish time to finish, the user is presented with a blank log backend regardless of the debug levels. Let's start processing logs earlier to avoid this issue. NOTE: Since this thread is now triggered specifically rather than started during static thread init, let's also name it. Signed-off-by: Michael Scott <mike@foundries.io> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Kconfig.template.log_config | ||
| log_backend_native_posix.c | ||
| log_backend_rtt.c | ||
| log_backend_uart.c | ||
| log_cmds.c | ||
| log_core.c | ||
| log_list.c | ||
| log_list.h | ||
| log_msg.c | ||
| log_output.c | ||
| sys_log_net.c | ||
| sys_log.c | ||