BUG: Debugger Does not Step Over to __finally Code Block

Last reviewed: May 21, 1997
Article ID: Q168379
The information in this article applies to:
  • The integrated debugger included with: - Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

The debugger does not Step-Over to code in __finally block from a __try block.

CAUSE

The __finally code is executed via a "call" instead of a "jmp instruction.

RESOLUTION

The workaround is to do a Step-Into (F11 key) instead of Step-Over (F10 key) in the debugger.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

Compile the following code with debug information.

    #include <iostream.h>

    void main ()
    {
   int counter=0;

    __try {
   counter++;//SET A BREAKPOINT HERE
   cout << "In try block" << endl;
          }

    __finally
          {
      counter++;
      cout << "In finally block" << endl;
          }

    cout << "Exit, counter=" << counter << endl;

    }

Set a breakpoint on the line shown above. Start the debugger with Debug Go or by pressing the F5 key. Step-Over (or, press F10) from that point onward. The debugger exits the program without going to the __finally block.


Keywords : kbtool vcbuglist500 WBDebug kbbuglist
Version : 5.0
Platform : NT WINDOWS
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.