zephyr/tests/kernel/fatal
Marc Herbert debade9121 tests: make find_package(Zephyr...) REQUIRED
... because it is (required).

This makes a difference when building with CMake and forgetting
ZEPHYR_BASE or not registering Zephyr in the CMake package registry.

In this particular case, REQUIRED turns this harmless looking log
statement:

-- Could NOT find Zephyr (missing: Zephyr_DIR)
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- ...
-- ...
-- ...
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:8 (target_sources):
  Cannot specify sources for target "app" which is not built by
  this project.

... into this louder, clearer, faster and (last but not least) final
error:

CMake Error at CMakeLists.txt:5 (find_package):
  Could not find a package configuration file provided by "Zephyr" with
  any of the following names:

    ZephyrConfig.cmake
    zephyr-config.cmake

  Add the installation prefix of "Zephyr" to CMAKE_PREFIX_PATH or set
  "Zephyr_DIR" to a directory containing one of the above files.  If
  "Zephyr" provides a separate development package or SDK, be sure it
  has been installed.

-- Configuring incomplete, errors occurred!

Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-05-29 10:47:25 +02:00
..
src kconfig: Rename CONFIG_FP_SHARING to CONFIG_FPU_SHARING 2020-05-08 10:58:33 +02:00
CMakeLists.txt tests: make find_package(Zephyr...) REQUIRED 2020-05-29 10:47:25 +02:00
prj_arm_fpu_sharing.conf tests: Rename kernel.common.stack_protection_arm_fp_sharing 2020-05-08 10:58:33 +02:00
prj_armv8m_mpu_stack_guard.conf tests: Never disable SMP 2019-09-26 16:54:06 -04:00
prj.conf tests: Never disable SMP 2019-09-26 16:54:06 -04:00
protection_no_userspace.conf tests: Never disable SMP 2019-09-26 16:54:06 -04:00
README
sentinel.conf tests: Never disable SMP 2019-09-26 16:54:06 -04:00
testcase.yaml tests: Rename kernel.common.stack_protection_arm_fp_sharing 2020-05-08 10:58:33 +02: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.