FIX: Remote Debugging Very Slow in Visual C++ Version 5.0

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

SYMPTOMS

Remote debugging in Visual C++ version 5.0 is very slow in establishing connection and doing Step Into (F11) and Step Over (F10).

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in Visual Studio 97 Service Pack 1.

For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Steps to Reproduce Behavior

Create a default MFC Appwizard project and build it for debug mode. Consult the online help on "Setting Up the Remote Debug Monitor" and the following article in the Microsoft Knowledge Bas to setup remote debugging: 

   ARTICLE-ID: Q131058
   TITLE     : Tips for Remote Debugging with Visual C++ 2.x and 4.0
Start the debugger by hitting the F5 (Debug Go) key or the F11 ( Step Into) key. Note that it may take about 25 to 30 seconds for the debugger to start. Subsequently, trying to Step Into or Step Over, or moving to the next break point may take up to 5 to 8 seconds. 
Keywords          : vcbuglist500 WBDebug VS97FixlistSP3 kbtool VS97FixlistSP2 VS97FixlistSP1
Version           : 5.0
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbservicepack

================================================================================

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: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.