Updated BLBackTrace::handler to print out a message for SIGILL

AMReX-Codes · Jul 27, 2023 · 65d34c7 · 65d34c7
1 parent a169a9b
commit 65d34c7
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/Docs/sphinx_documentation/source/Debugging.rst b/Docs/sphinx_documentation/source/Debugging.rst
@@ -27,7 +27,7 @@ use of uninitialized values, AMReX also initializes ``FArrayBox``\ s in
 ``MulitFab``\ s and arrays allocated by ``bl_allocate`` to signaling NaNs when it is compiled
 with ``TEST=TRUE`` or ``DEBUG=TRUE`` in GNU make, or with ``-DCMAKE_BUILD_TYPE=Debug`` in CMake.
 One can also control the setting for ``FArrayBox`` using the runtime parameter, ``fab.init_snan``.
-Note for Macs, M1 and M2 chips using Arm64 architecture are not able to trap division by zero.  
+Note for Macs, M1 and M2 chips using Arm64 architecture are not able to trap division by zero.
 
 One can get more information than the backtrace of the call stack by
 instrumenting the code.  Here is an example.

diff --git a/Src/Base/AMReX_BLBackTrace.cpp b/Src/Base/AMReX_BLBackTrace.cpp
@@ -58,6 +58,9 @@ BLBackTrace::handler(int s)
     case SIGFPE:
         amrex::ErrorStream() << "Erroneous arithmetic operation\n";
         break;
+    case SIGILL:
+        amrex::ErrorStream() << "SIGILL Invalid, privileged, or ill-formed instruction\n";
+        break;
     case SIGTERM:
         amrex::ErrorStream() << "SIGTERM\n";
         break;