Lines Matching +full:line +full:- +full:addresses

10 either build-time checks, conditionally compiled assertions, or deliberately
21 non-zero value. There are two ways to do this:
23 - Use the :kconfig:option:`CONFIG_ASSERT` and :kconfig:option:`CONFIG_ASSERT_LEVEL` kconfig
25 - Add ``-D__ASSERT_ON=<level>`` to the project's CFLAGS, either on the
26   build command line or in a CMakeLists.txt.
32 the kernel contains debug-type ``__ASSERT()`` statements; this reminder is
46 ----------
53 file and line number where the assertion can be found.
57 .. code-block:: c
64 .. code-block:: none
77 ---------------
91 .. code-block:: c
100 .. code-block:: c
113 -----------------
123 Zephyr provides two macros for performing build-time assertion checks.
124 These are evaluated completely at compile-time, and are always checked.
127 --------------
135 :c:func:`printf()`-like format codes or extra arguments.
139 .. code-block:: c
145 .. code-block:: none
183 If the CPU receives a hardware interrupt on an interrupt line that has not had
197 addresses outside of the stack buffer. Because this is enforced by the
206 implemented via dedicated CPU features, or read-only MMU/MPU guard regions
213 :kconfig:option:`CONFIG_STACK_SENTINEL` is a software-only stack overflow detection