Rule Definition
If a program throws an unhandled exception it terminates in an implementation-defined manner. In particular, it is implementation-defined whether the call stack is unwound, before termination, so the destructors of any automatic objects may or may not be executed. By enforcing the provision of a “last-ditch catch-all”, the developer can ensure that the program terminates in a consistent manner. This rule’s objective is to ensure that exceptions that were not expected are also caught.

Remediation
Add a catchall handler in the main function

Violation Code Sample

int32_t main( )
{
try
{
// program code
}
catch 
{
//handle runtime exception
}
return 0;
}

Fixed Code Sample

int32_t main( )
{
try
{
// program code
}
catch ( ... ) // Catch-all handler
{
// Handle unexpected exceptions
}
return 0;
}

MISRA C++ 2008, 15-3-2: There should be at least one exception handler to catch all otherwise unhandled exceptions AUTOSAR C++ 2014, Rule A15-3-3: There shall be at least one exception handler to catch all otherwise unhandled exceptions.