From 1906a36a8635fe8f666bc60eab354274ffc8dcfa Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Sun, 18 Nov 2012 19:51:10 +0100 Subject: score: Change _Internal_error_Occurred() Call the fatal handlers of the user extensions before the update of _Internal_errors_What_happened. This reduces the requirements on the execution context further. Now a valid read-write data is only required after the call to the fatal handlers. --- doc/user/fatal.t | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc') diff --git a/doc/user/fatal.t b/doc/user/fatal.t index aa9c2bf0a6..42a2432b1e 100644 --- a/doc/user/fatal.t +++ b/doc/user/fatal.t @@ -9,9 +9,9 @@ @section Introduction -The fatal error manager processes all fatal or -irrecoverable errors. The directive provided by the fatal error -manager is: +The fatal error manager processes all fatal or irrecoverable errors and other +sources of system termination (for example after exit()). The directives +provided by the fatal error manager are: @itemize @bullet @item @code{@value{DIRPREFIX}fatal_error_occurred} - Invoke the fatal error handler @@ -40,7 +40,7 @@ upon detection of an error it considers to be fatal. Similarly, the user should invoke the fatal error manager upon detection of a fatal error. -Each status or dynamic user extension set may include +Each static or dynamic user extension set may include a fatal error handler. The fatal error handler in the static extension set can be used to provide access to debuggers and monitors which may be present on the target hardware. If any -- cgit v1.2.3