This handler encapsulates functionality which provides the foundation Semaphore services used in all of the APIs supported by RTEMS. More...
|
Data Structures | |
| struct | Internal_errors_Information |
| This type holds the fatal error information. More... | |
Typedefs | |
| typedef uint32_t | Internal_errors_t |
Enumerations | |
| enum | Internal_errors_Source { INTERNAL_ERROR_CORE, INTERNAL_ERROR_RTEMS_API, INTERNAL_ERROR_POSIX_API, RTEMS_FATAL_SOURCE_BDBUF, RTEMS_FATAL_SOURCE_APPLICATION, RTEMS_FATAL_SOURCE_EXIT, RTEMS_FATAL_SOURCE_BSP_GENERIC, RTEMS_FATAL_SOURCE_BSP_SPECIFIC, RTEMS_FATAL_SOURCE_ASSERT, RTEMS_FATAL_SOURCE_STACK_CHECKER, RTEMS_FATAL_SOURCE_EXCEPTION, RTEMS_FATAL_SOURCE_LAST = 0xffffffff } |
| This type lists the possible sources from which an error can be reported. More... | |
| enum | Internal_errors_Core_list { INTERNAL_ERROR_NO_CONFIGURATION_TABLE, INTERNAL_ERROR_NO_CPU_TABLE, INTERNAL_ERROR_TOO_LITTLE_WORKSPACE, INTERNAL_ERROR_WORKSPACE_ALLOCATION, INTERNAL_ERROR_INTERRUPT_STACK_TOO_SMALL, INTERNAL_ERROR_THREAD_EXITTED, INTERNAL_ERROR_INCONSISTENT_MP_INFORMATION, INTERNAL_ERROR_INVALID_NODE, INTERNAL_ERROR_NO_MPCI, INTERNAL_ERROR_BAD_PACKET, INTERNAL_ERROR_OUT_OF_PACKETS, INTERNAL_ERROR_OUT_OF_GLOBAL_OBJECTS, INTERNAL_ERROR_OUT_OF_PROXIES, INTERNAL_ERROR_INVALID_GLOBAL_ID, INTERNAL_ERROR_BAD_STACK_HOOK, INTERNAL_ERROR_BAD_ATTRIBUTES, INTERNAL_ERROR_IMPLEMENTATION_KEY_CREATE_INCONSISTENCY, INTERNAL_ERROR_IMPLEMENTATION_BLOCKING_OPERATION_CANCEL, INTERNAL_ERROR_MUTEX_OBTAIN_FROM_BAD_STATE, INTERNAL_ERROR_UNLIMITED_AND_MAXIMUM_IS_0, INTERNAL_ERROR_SHUTDOWN_WHEN_NOT_UP, INTERNAL_ERROR_GXX_KEY_ADD_FAILED, INTERNAL_ERROR_GXX_MUTEX_INIT_FAILED, INTERNAL_ERROR_NO_MEMORY_FOR_HEAP, INTERNAL_ERROR_CPU_ISR_INSTALL_VECTOR } |
| A list of errors which are generated internally by the executive core. | |
Functions | |
| void | _Internal_error_Occurred (Internal_errors_Source the_source, bool is_internal, Internal_errors_t the_error) RTEMS_COMPILER_NO_RETURN_ATTRIBUTE |
| Initiates system termination. | |
Variables | |
| Internal_errors_Information | _Internal_errors_What_happened |
| When a fatal error occurs, the error information is stored here. | |
Detailed Description
This handler encapsulates functionality which provides the foundation Semaphore services used in all of the APIs supported by RTEMS.
Enumeration Type Documentation
This type lists the possible sources from which an error can be reported.
- Enumerator:
RTEMS_FATAL_SOURCE_BDBUF Fatal source for the block device cache.
- See also:
- rtems_bdbuf_fatal_code.
RTEMS_FATAL_SOURCE_APPLICATION Fatal source for application specific errors.
The fatal code is application specific.
RTEMS_FATAL_SOURCE_EXIT Fatal source of exit().
The fatal code is the exit() status code.
RTEMS_FATAL_SOURCE_BSP_GENERIC Fatal source for generic BSP errors.
The fatal codes are defined in <bsp/bootcard.h>. Examples are interrupt and exception initialization.
- See also:
- bsp_generic_fatal_code.
RTEMS_FATAL_SOURCE_BSP_SPECIFIC Fatal source for BSP specific errors.
The fatal code is BSP specific.
RTEMS_FATAL_SOURCE_ASSERT Fatal source of assert().
The fatal code is the pointer value of the assert context.
- See also:
- rtems_assert_context.
RTEMS_FATAL_SOURCE_STACK_CHECKER Fatal source of the stack checker.
The fatal code is the object name of the executing task.
RTEMS_FATAL_SOURCE_EXCEPTION Fatal source of the exceptions.
The fatal code is the pointer value of the exception frame pointer.
- See also:
- rtems_exception_frame and rtems_exception_frame_print().
RTEMS_FATAL_SOURCE_LAST The last available fatal source.
This enum value ensures that the enum type needs at least 32-bits for architectures with short enums.
Function Documentation
| void _Internal_error_Occurred | ( | Internal_errors_Source | the_source, |
| bool | is_internal, | ||
| Internal_errors_t | the_error | ||
| ) |
Initiates system termination.
This routine is invoked when the application or the executive itself determines that a fatal error has occurred or a final system state is reached (for example after exit()).
The first action of this function is to call the fatal handler of the user extensions. For the initial extensions the following conditions are required
- a valid stack pointer and enough stack space,
- a valid code memory, and
- valid read-only data.
For the initial extensions the read-write data (including BSS segment) is not required.
Non-initial extensions require in addition valid read-write data. The BSP may install an initial extension that performs a system reset. In this case the non-initial extensions will be not called.
Once all fatal handler executed the error information will be stored to _Internal_errors_What_happened and the system state is set to SYSTEM_STATE_FAILED.
The final step is to call the CPU specific _CPU_Fatal_halt().
- Parameters:
-
[in] the_source The fatal source indicating the subsystem the fatal condition originated in. [in] is_internal Indicates if the fatal condition was generated internally to the executive. [in] the_error The fatal error code. This value must be interpreted with respect to the source.
- See also:
- rtems_fatal_error_occurred() and rtems_fatal().
