Visual C++ Debugger Stops Responding on Windows 2000 When Running on Multiple Processor Computers

This article was previously published under Q310787
This article has been archived. It is offered "as is" and will no longer be updated.
When you use the Visual C++ 6.0 debugger on a multi-processor computer that has Microsoft Windows 2000 and Windows 2000 Service Pack 2 installed, the Visual C++ development environment may stop responding.
The Visual C++ 6.0 debugger stops responding because of a bug in the debugger logic. This problem occurs when the debugger responds to debugging events that are sent from Windows 2000.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
Date          Time      Version       Size            File name ----------------------------------------------------------------22-Oct-2001   19:14     6.0.9388.0    106,566 bytes   Dm.dll             					
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
hang multiprocessor win2k

Article ID: 310787 - Last Review: 01/10/2015 13:20:26 - Revision: 3.2

Microsoft Visual C++ 6.0 Service Pack 5

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbdebug kbfix kbide kbqfe KB310787