CONFIG_THREAD_ANALYZER_RUN_UNLOCKED

Run analysis with interrupts unlocked

Type: bool

Help

The thread analysis takes quite a long time.
Every thread it finds is analyzed word by word to find any that
does not match the magic number.
Normally while thread are analyzed the k_thread_foreach function
is used.
While this is a safe run from the thread list perspective it may lock
the interrupts for a long time - long enough to disconnect when
Bluetooth communication is used.
Setting this flag will force thread analyzer to use
the k_thread_foreach_unlocked function.
This will allow the interrupts to be processed while the thread is
analyzed.
For the limitation of such configuration see the k_thread_foreach
documentation.

Direct dependencies

THREAD_ANALYZER

(Includes any dependencies from ifs and menus.)

Default

y

Kconfig definition

At <Zephyr>/subsys/debug/Kconfig:42

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:44 → <Zephyr>/subsys/Kconfig:17

Menu path: (Top) → Sub Systems and OS Services → System Monitoring Options → Enable Thread analyzer

config THREAD_ANALYZER_RUN_UNLOCKED
    bool "Run analysis with interrupts unlocked"
    default y
    depends on THREAD_ANALYZER
    help
      The thread analysis takes quite a long time.
      Every thread it finds is analyzed word by word to find any that
      does not match the magic number.
      Normally while thread are analyzed the k_thread_foreach function
      is used.
      While this is a safe run from the thread list perspective it may lock
      the interrupts for a long time - long enough to disconnect when
      Bluetooth communication is used.
      Setting this flag will force thread analyzer to use
      the k_thread_foreach_unlocked function.
      This will allow the interrupts to be processed while the thread is
      analyzed.
      For the limitation of such configuration see the k_thread_foreach
      documentation.

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