C++ try-catch block doesn't catch hardware exception

Question

I'm examining hardware and software exceptions in visual studio 2013. I know that I can catch hardware exceptions by setting 'Enable C++ Exceptions' option to /EHa (Yes with SEH Exceptions). I'm trying to catch the following exceptions:

EXCEPTION_ARRAY_BOUNDS_EXCEEDED - didn't catch

EXCEPTION_ACCESS_VIOLATION - caught

EXCEPTION_INT_OVERFLOW - didn't catch

EXCEPTION_INT_DIVIDE_BY_ZERO - caught

This is an example of code.

try {
    a = std::numeric_limits<int>::max();
    a += 5;
}
catch (...){

    std::cout << "EXCEPTION_INT_OVERFLOW Exception Caught" << std::endl;
    exit(1);
}

try {
    int h = 0;
    b = b / h;
}
catch (...){

    std::cout << "EXCEPTION_INT_DIVIDE_BY_ZERO Exception Caught" << std::endl;
    exit(1);
}

It catches only divide by zero exception. Is this dependent of processor, or there is something else? One more little question, is there any difference between debug and release builds?

Mathia

According to this, you need to use __try __except. See msdn.microsoft.com/en-us/library/ms681409%28v=vs.85%29.aspx – Icterus

@RobertHarvey: No, /EHa causes C++ exception handling to use Structured Exception Handling and OS exceptions will be caught by catch (...) – Wikiup

Answer 1

Is this dependent of processor

Yup. The OS only maps hardware traps to structured exceptions, it doesn't add logic to detect conditions that the hardware doesn't. (On the other hand, managed frameworks such as the JVM or CLR often do add logic. Catching these in software of course carries a performance penalty, while hardware trap logic is free unless the trap actually occurs.)

Now, this isn't to say that you cannot receive EXCEPTION_INT_OVERFLOW on x86 processors. But the conditions are not what you expect -- mere wraparound during addition does not cause a trap. See Raymond Chen's blog entry:

• In the red corner, EXCEPTION_INT_DIVIDE_BY_ZERO and STATUS_INTEGER_DIVIDE_BY_ZERO; and in the blue corner, EXCEPTION_INT_and STATUS_INTEGER_OVERFLOW

Wikiup