PRB: Debugger Loses Source/Disassembly File Mapping

• The integrated debugger included with: - Microsoft Visual C++, 32-bit Edition, versions 2.0, 2.1, 4.0, 5.0

SYMPTOMS

If you choose Cancel when asked for the location of a source file while debugging, you will not get another chance to map the disassembly code to its corresponding source file.

For example, suppose that you have moved a source file belonging to the debug version of a program to some other directory. When you step into that code in the debugger, you will get a dialog box asking where the source file is located. If you then choose to Cancel that dialog box, a Disassembly window will be opened for the source. If you continue debugging and later step through the code that causes the same source file to be opened again, Visual C++ will automatically open up the Disassembly window and will not ask again for the source location.

CAUSE

In trying to prevent asking the user for a file's location over and over again, Visual C++ does not display the dialog box again if you chose Cancel the first time. If you subsequently decide that you really do want to see the source for a file, you must follow the steps listed below in the Resolution section.

RESOLUTION

To work around this behavior:

1. Close the Disassembly window.

2. Open the source file in an editor window.

3. Step into the code generated by that source, or double-click the current frame (the top) of the call stack. In Visual C++ 2.x, the Call Stack window can be opened by selecting Debug | Call Stack from the Visual Workbench main menu. In Visual C++ 4.0, the Call Stack window can be opened by choosing Call Stack from the View menu. This step reestablishes the source link.

STATUS

This behavior is by design.