Help¶

If new buffer for a log message cannot be allocated in that time, log message is dropped. Forever blocking (-1) is possible however may lead to the logger deadlock if logging is enabled in threads used for logging (e.g. logger or shell thread).

Direct dependencies¶

LOG_BLOCK_IN_THREAD && !LOG_IMMEDIATE && !LOG_MINIMAL && LOG

(Includes any dependencies from ifs and menus.)

Default¶

1000

Kconfig definition¶

At <Zephyr>/subsys/logging/Kconfig:168

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:28

Menu path: (Top) → Sub Systems and OS Services → Logging → On log full block in thread context

config LOG_BLOCK_IN_THREAD_TIMEOUT_MS
    int "Maximum time (in milliseconds) thread can be blocked"
    range -1 10000
    default 1000
    depends on LOG_BLOCK_IN_THREAD && !LOG_IMMEDIATE && !LOG_MINIMAL && LOG
    help
      If new buffer for a log message cannot be allocated in that time, log
      message is dropped. Forever blocking (-1) is possible however may lead
      to the logger deadlock if logging is enabled in threads used for
      logging (e.g. logger or shell thread).

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)