zephyr/tests/kernel/fatal
Ioannis Glaropoulos f3f3dc8768 tests: kernel: fatal: run test for ARMv8-M with MPU stack guards
HW stack protection in ARMv8-M is implemented by default
with the built-in stack guard mechanism. Therefore, by
default all tests for ARMv8-M will use the built-in stack
overflow mechanism (CONFIG_BUILTIN_STACK_GUARD is set in
tests). However, we would like have some coverage on the
MPU stack guard mechanism for ARMv8-M. The added test case
manually disables BUILTIN_STACK_GUARD and enables the
MPU_STACK_GUARD option, to provide that test coverage.

Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2019-07-01 12:54:20 -07:00
..
src tests: kernel: fatal: check stack overflow of FP capable threads 2019-06-27 18:07:03 -07:00
CMakeLists.txt license: cleanup: add SPDX Apache-2.0 license identifier 2019-04-07 08:45:22 -04:00
prj_arm_fp_sharing.conf tests: remove redundant CONFIG_HW_STACK_PROTECTION=y setting 2019-07-01 12:54:20 -07:00
prj_armv8m_mpu_stack_guard.conf tests: kernel: fatal: run test for ARMv8-M with MPU stack guards 2019-07-01 12:54:20 -07:00
prj.conf tests: remove redundant CONFIG_HW_STACK_PROTECTION=y setting 2019-07-01 12:54:20 -07:00
protection_no_userspace.conf tests: remove redundant CONFIG_HW_STACK_PROTECTION=y setting 2019-07-01 12:54:20 -07:00
README
sentinel.conf tests: CONFIG_TEST_USERSPACE now off by default 2019-04-06 14:30:42 -04:00
testcase.yaml tests: kernel: fatal: run test for ARMv8-M with MPU stack guards 2019-07-01 12:54:20 -07:00

This test case verifies that kernel fatal error handling works correctly.

If a thread causes a CPU exception, and it is not in an ISR or "essential"
thread, the thread gets aborted and the rest of the system executes normally.