Microsoft KB Archive/141040

= BUG: Step Out in Debugger Ignores Try/Catch Scope =

Article ID: 141040

Article Last Modified on 12/9/2003

-

APPLIES TO

 The Integrated Debugger, when used with:  Microsoft Visual C++ 4.0 Professional Edition

 Microsoft Visual C++ 4.1 Subscription

 Microsoft Visual C++ 4.2 Professional Edition

 Microsoft Visual C++ 4.2 Enterprise Edition</li></ul>

 Microsoft Visual C++ 5.0 Learning Edition</li></ul>

 Microsoft Visual C++ 5.0 Learning Edition</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q141040

<div class="symptoms_section">

SYMPTOMS
The debug Step Out command does not step you to the expected function when used within try/catch blocks.

<div class="resolution_section">

RESOLUTION
As an alternative to Step Out, use one of the other debug step options such as Run to Cursor or Step Over.

<div class="status_section">

STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ version 5.0.

<div class="moreinformation_section">

MORE INFORMATION
When you debug an application that uses either the C++ try or catch keywords or the MFC TRY or CATCH macros, attempting to step out of the try or catch block results in popping two frames off the stack. While executing code within the try block or the catch block, Step Out should step you out of the block and into the function that contains the try/catch blocks. Step Out instead takes you to the function that called the function containing the try/catch blocks.

Additional query words: kbVC400bug shift f11 f7

Keywords: kbbug kbide kbdebug KB141040

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.