Microsoft KB Archive/247203

From BetaArchive Wiki

Article ID: 247203

Article Last Modified on 1/22/2004


  • Microsoft Visual C++ 6.0 Enterprise Edition
  • Microsoft Visual C++ 6.0 Professional Edition
  • Microsoft Visual C++ 6.0 Standard Edition

This article was previously published under Q247203


When trying to build an application that uses C++ exception handling, with global optimizations enabled, the catch handler within the try/catch block may not catch any of the exceptions that are thrown by the instructions in the try block. See the "More Information" section below for details.


The optimizer optimizes the try/catch block incorrectly.


Here are the two ways to work around this problem:

  1. Disable global optimizations on a function-by-function basis using the optimize pragma with the "g" option. /Og- disables global optimization on a file-by-file basis.
  2. Use the asynchronous exception handling model by specifying the /EHa compiler option.


This bug was corrected in Microsoft Visual C++ .NET 2002.


Steps to Reproduce Behavior

Compile Options : cl /GX /GR /Og test.cpp

#include <iostream>
using namespace std;

class CObject
    virtual function() {};  //necessary to make the class polymorphic

class B : public CObject
    CObject* m_pComp;
    void Test() const;

void B::Test() const
    B* pComp;
    catch(exception& exc)   //The exception is caught only if Global Optimizations are disabled.
        cout << "In Catch Block\n";
        cout << "Exception Caught\n" <<endl;

void main()
    B object;   //m_pComp is intentionally not initialized so that the exception occurs.

Expected Output:
In Catch Block
Exception Caught


When the above code is compiled using /Og, then the control never enters the catch block and results in an access violation.

Keywords: kbbug kbpending KB247203