FIX: Debugger Performance Problem Using Unresolved Break Points

When you debug a Visual C++ .NET application with unresolved break points, the application is slow to start in the debugger. In the output window, the messages that indicate that a module has been loaded are also slow to appear. The performance slows down when you have a large number of unresolved break points in large number of modules.

When you set break points in DLLs (that are loaded by your application when you open the corresponding source files, and then press F9), your break points are unresolved. You can avoid this problem in Visual C++ 6.0, when you specify Additional DLLs on the Debug tab of the Project Setting dialog box.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .Net service pack that contains this hotfix.

To resolve this problem immediately, 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 has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.