FIX: Old address in Memory window may cause unhandled exception in Visual Studio .NET (319837)
The information in this article applies to:
- Microsoft Visual Studio .NET (2002), Professional Edition SP1
- Microsoft Visual Studio .NET (2002), Enterprise Architect Edition SP1
- Microsoft Visual Studio .NET (2002), Enterprise Developer Edition SP1
- Microsoft Visual Studio .NET (2002), Academic Edition SP1
This article was previously published under Q319837 SYMPTOMS When you debug a managed application, a memory address that
is left in the Memory window from a previous debug session may cause the
debugger to generate an unhandled exception. This problem only occurs in
managed applications if the expression that is left in the Memory window is a function + offset expression. RESOLUTION If the debugger does not generate an unhandled exception
immediately when you start the debugger, follow these steps to work around this
problem:
- Press F10 to step into Main.
- Set the expression in the Memory window to 0.
- Press F10 again to continue stepping through your
code.
If the exception occurs immediately when you start the
debugger, try to create a new Microsoft Visual C# .NET or Microsoft Visual
Basic .NET Console Application project, and then reset the garbage value in the
Address box of the Memory window by using this project:
- Create a new default Visual C# .NET or Visual Basic .NET
Console Application project.
- Press F10 to step into Main.
- Set the expression in the Memory window to 0.
- Stop debugging. This clears the old value that was causing
the problem in the Address box of the Memory window.
- Load your original project that causes the exception, and
then step through the code.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
This bug was corrected in all versions of Microsoft Visual Studio .NET (2003).
Modification Type: | Minor | Last Reviewed: | 8/29/2005 |
---|
Keywords: | kbvs2002sp1sweep kbfix kbBug kbDebug KB319837 |
---|
|