Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

MISRA.CATCH.ALL

No ellipsis exception handler in a try-catch block.

MISRA-C++ Rule 15-3-2 (advisory): There should be at least one exception handler to catch all otherwise unhandled exceptions.

[Implementation 15.3(9), 15.5.1(2)]

Rationale

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.

The objective of Rule 15—3—4 is that a program should catch all exceptions that it is expected to throw. This rule"™s objective is to ensure that exceptions that were not expected are also caught.

Example

For the majority of programs this will mean main should look like:

int32_t main( )
{
   try
   {
      // program code
   }

   catch ( ... ) // Catch-all handler
   {
      // Handle unexpected exceptions
   }
   return 0;
}