VS Debugger seems to hang when you start debugging

VS Debugger seems to hang when you start debugging

Article ID : 951336
Last Review : April 4, 2008
Revision : 1.0
Source: Microsoft Support

Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

Action

Create a simple MFC application in Visual Studio 2003 / 2005/ 2008. Start debugging by pressing F5.

Back to the top

Result

Visual Studio debugger takes a long time to start debugging the application.  This gives an impression that Visual Studio has hung.

Back to the top

Cause

Invalid symbol path location, or a geographically distant location where symbols are stored, causing high network latency.

 

Back to the top

Resolution

Check if the _NT_SYMBOL_PATH environment variable contains valid information.

In the Visual Studio IDE, goto Tools->Options->Debugging->Symbols->Symbol File (.pdb) locations. Check if you have valid path here.

If you do have a valid path in either of these locations, try removing these entries to see if that helps.  If the problem goes away, then you may have a high network latency causing delayed load of symbols and slow debugger startup/response times.

Back to the top

More Information

When the debugger starts up, it tries to load the PDB symbol files for loaded modules.  High network latency can cause Visual Studio to become unresponsive.  A local symbol cache can be used to work around the problem.

Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top


APPLIES TO
• Microsoft Visual Studio .NET 2003 Academic Edition
• Microsoft Visual Studio .NET 2003 Enterprise Architect
• Microsoft Visual Studio .NET 2003 Enterprise Developer
• Microsoft Visual Studio 2005 Professional Edition
• Microsoft Visual Studio 2005 Standard Edition
• Microsoft Visual Studio 2005 Team Suite
• Microsoft Visual Studio 2008 Professional Edition
• Microsoft Visual Studio 2008 Academic Edition
• Microsoft Visual Studio 2008 Standard Edition
• Microsoft Visual Studio Team System 2008 Team Suite

Back to the top

Keywords: 
kbnomt kbrapidpub kbmbsdevelopmenttools KB951336

Back to the top

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image