Rule Definition
If an exception object of pointer type is thrown and that pointer refers to a dynamically created object, then it may be unclear which function is responsible for destroying it, and when. This ambiguity does not exist if the object is caught by value or reference.

Remediation
It is recommended that exceptions should always be thrown by value.

Violation Code Sample

class A
{
// Implementation
};
void fn ( int16_t i )
{
static A a1;
A * a2 = new A;
if ( i > 10 )
{
throw ( &a1 ); // Non-compliant – pointer type thrown
}
else
{
throw ( a2 ); // Non-compliant – pointer type thrown
}
}

Fixed Code Sample

class A
{
// Implementation
};
void fn ( int16_t i )
{
static A a1;
if ( i > 10 )
{
throw ( a1 ); // Compliant – thrown by value
}
.
.
.

MISRA 2008 C++, 15-0-2: An exception object should not have pointer type.