CONFIG_BT_ASSERT_PANIC

Use k_panic() instead of k_oops()

Type: bool

Help

When CONFIG_BT_ASSERT is enabled, this option makes the code call
k_panic() instead of k_oops() when an assertion is triggered.

Help

When CONFIG_BT_ASSERT is enabled, this option makes the code call
k_panic() instead of k_oops() when an assertion is triggered.

Direct dependencies

(BT_ASSERT && BT_RPC_STACK) || (BT_ASSERT && BT_HCI && BT)

(Includes any dependencies from ifs and menus.)

Defaults

No defaults. Implicitly defaults to n.

Kconfig definitions

At <Zephyr>/subsys/bluetooth/common/Kconfig:257

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:92 → <nRF>/subsys/Kconfig:10 → <nRF>/subsys/bluetooth/Kconfig:38 → <nRF>/subsys/bluetooth/rpc/Kconfig:195

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Bluetooth Low Energy → BLE over nRF RPC → Custom Bluetooth assert implementation

config BT_ASSERT_PANIC
    bool "Use k_panic() instead of k_oops()"
    depends on BT_ASSERT && BT_RPC_STACK
    help
      When CONFIG_BT_ASSERT is enabled, this option makes the code call
      k_panic() instead of k_oops() when an assertion is triggered.

At <Zephyr>/subsys/bluetooth/common/Kconfig:257

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:44 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:179

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Custom Bluetooth assert implementation

config BT_ASSERT_PANIC
    bool "Use k_panic() instead of k_oops()"
    depends on BT_ASSERT && BT_HCI && BT
    help
      When CONFIG_BT_ASSERT is enabled, this option makes the code call
      k_panic() instead of k_oops() when an assertion is triggered.

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