Page History

The C++ Standard, [except.handle], paragraph 4 [ISO/IEC 14882-2014], states the following:

The handlers for a try block are tried in order of appearance. That makes it possible to write handlers that can never be executed, for example by placing a handler for a derived class after a handler for a corresponding base class.

Consequently, if two handlers catch exceptions that are derived from the same base class (such as std::exception), the most derived exception must come first.

...

Exception handlers with inverted priorities cause unexpected control flow when an exception of the derived type occurs.

Rule	Severity	Likelihood	Remediation Cost	Priority	Level
ERR54-CPP	Medium	Likely	Low	P18	L1

Automated Detection

Tool

Version

Checker

Description

Astrée

Include Page

	Astrée_V
	Astrée_V

exception-caught-by-earlier-handler

Fully checked

Axivion Bauhaus Suite

Include Page

	Axivion Bauhaus Suite_V
	Axivion Bauhaus Suite_V

CertC++-ERR54

Clang

Include Page

	Clang_V
	Clang_V

-Wexceptions

CodeSonar

Include Page

	CodeSonar_V
	CodeSonar_V

LANG.STRUCT.UCTCH

Unreachable Catch

ECLAIR

Include Page

	ECLAIR_V
	ECLAIR_V

CP1.ERR36

Fully implemented

PRQA QA-

Helix QAC

Include Page

	Helix QAC_V
	Helix QAC_V

C++4030, C++4639

Klocwork

Include Page

	Klocwork_V
	Klocwork_V

MISRA.CATCH.NOALL
MISRA.CATCH.WRONGORD

LDRA tool suite

Include Page

	LDRA_V
	LDRA_V

541 S, 556 S

Fully implemented

Parasoft C/C++test

Include Page

PRQA QA-C++_VPRQA QA-C++_V4040, 4034

	Parasoft_V
	Parasoft_V

CERT_CPP-ERR54-a

Where multiple handlers are provided in a single try-catch statement or function-try-block for a derived class and some or all of its bases, the handlers shall be ordered most-derived to base class

Polyspace Bug Finder

Include Page