[rtems-docs commit] c-user: Remove _Internal_errors_What_happened
Sebastian Huber
sebh at rtems.org
Wed Jul 28 06:46:44 UTC 2021
Module: rtems-docs
Branch: master
Commit: 18746fb259c585442e2f6e893e2ab8900aa50d0c
Changeset: http://git.rtems.org/rtems-docs/commit/?id=18746fb259c585442e2f6e893e2ab8900aa50d0c
Author: Sebastian Huber <sebastian.huber at embedded-brains.de>
Date: Wed Jul 28 08:45:41 2021 +0200
c-user: Remove _Internal_errors_What_happened
This global object no longer exists.
---
c-user/fatal-error/operations.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/c-user/fatal-error/operations.rst b/c-user/fatal-error/operations.rst
index 77753d6..6d03a26 100644
--- a/c-user/fatal-error/operations.rst
+++ b/c-user/fatal-error/operations.rst
@@ -40,12 +40,11 @@ The fatal extensions are called with three parameters:
- the fatal source,
-- a legacy parameter which is always false, and
+- a legacy parameter which is always set to :c:macro:`false`, and
- an error code with a fatal source dependent content.
-Once all fatal extensions executed, the error information will be stored to
-:c:data:`_Internal_errors_What_happened` and the system state is set to
+Once all fatal extensions executed, the system state is set to
:c:macro:`SYSTEM_STATE_TERMINATED`.
The final step is to call the CPU port specific :c:func:`_CPU_Fatal_halt()`.
More information about the vc
mailing list