Article ID: 957912 - View products that this article applies to.
Microsoft has released updates for Microsoft Visual Studio 2008 SP1 debugger components. These updates mostly address issues that occur with stepping and with hitting breakpoints.
InstallationThis update is for all versions of Visual Studio 2008 SP1 on both x86 and x64 computers. However, if you use Visual Studio 2008 Standard Edition on a 64-bit operating system, you must install the 64-bit Visual Studio 2008 SP1 Remote Debugger before you apply this update. For information about how to obtain the 64-bit Visual Studio 2008 SP1 Remote Debugger, visit the following Microsoft Web site:
Multi-process and multi-threaded debugger fixesNote The following descriptions refer to a hypothetical set of processes that are being debugged by a single instance of Visual Studio. When functions are referred, it is assumed that the functions are recursive or that the functions contain loops. These scenarios are not meant to reproduce the problem. Instead, they are provided to help explain the problem.
Breakpoints in parallelized loops are eventually ignored after multiple hitsBreakpoints put in loops or in recursive functions are not hit in all processes at each iteration. Frequently, some processes may pass through many iterations of a loop, ignoring the breakpoint, before a process is stopped. Consider the following scenario:
Stopping and starting threads causes breakpoints to be missedBreakpoints are hit, but they are not visible when you debug multiple processes in the Visual Studio debugger. Consider the following scenario in which you are debugging two processes, Process A and Process B.
Note If you remove the breakpoints after you press F5 to continue, the debugger runs until it is completed.
Visual Studio may crash when you debug multiple processes at the same timeVisual Studio Debugger may experience a deadlock when you start and then stop a thread and then run to the next breakpoint if multiple processes are being debugged. Consider the following scenario:
Stepping over a disabled breakpoint when you debug a native application turns into a "go"You debug a native application in Visual Studio that contains a disabled breakpoint. When you step the debugger past the disabled breakpoint, the remaining steps are lost, and the application continues to run.
Stepping when you debug a managed multithreaded application can randomly turn into a "go"When you debug a multithreaded managed application, and you step into one thread while an event occurs with another thread, such as hitting a breakpoint, the step request is lost. And, the application continues to run.
Message Passing Interface (MPI) Debugger Fixes for Visual Studio Editions offering MPI-Plugin Support
Visual Studio crashes when you use the "Step Into" command to start an MPI programWhen you use the Step into command, or press F11, to debug multiple instances of an MPI process, Visual Studio crashes. Or, you receive the following error message:
Microsoft Visual Studio has encountered and internal error
Running the "Step Over" command while you are debugging multiple processes causes a deadlockIf you run the Step Over command while you are debugging multiple processes, Visual Studio crashes. Consider the following scenario:
Breakpoint UI Fix
Disabled breakpoints are not visible after you install Visual Studio 2008 Service Pack 1If you disable a breakpoint, the breakpoint is no longer hit. Also, the breakpoint is hidden from the left-most editor channel. The disabled breakpoint still exists. It is displayed in the Breakpoints Tool window.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesYou must have Microsoft Visual Studio 2008 SP1 installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 957912 - Last Review: February 4, 2009 - Revision: 2.0
Contact us for more help