Lines Matching refs:kernel
32 the kernel contains debug-type ``__ASSERT()`` statements; this reminder is
41 a default implementation with weak linkage which invokes a kernel oops if
42 the thread that failed the assertion was running in user mode, and a kernel
48 The ``__ASSERT()`` macro can be used inside kernel and application code to
51 to provide context to the assertion. In addition, the kernel will print
66 ASSERTION FAIL [foo == 0xF0CACC1A] @ ZEPHYR_BASE/tests/kernel/fatal/src/main.c:367
79 The ``__ASSERT_EVAL()`` macro can also be used inside kernel and application
147 tests/kernel/fatal/src/main.c: In function 'test_main':
151 tests/kernel/fatal/src/main.c:370:2: note: in expansion of macro 'BUILD_ASSERT'
158 A kernel oops is a software triggered fatal error invoked by
167 A kernel error is a software triggered fatal error invoked by
168 :c:func:`k_panic()`. This should be used to indicate that the Zephyr kernel is
170 :c:func:`k_sys_fatal_error_handler()` should not return if the kernel
174 and doing so will generate a kernel oops instead. Otherwise, the fatal error
185 then the kernel will generate a fatal error with the reason code
192 stack buffer provides, the kernel may be able to detect this situation and