Microsoft KB Archive/92605
FIX: CVW Breakpoint Missed Debugging Two Applications
The information in this article applies to:
- Microsoft CodeView for Windows, versions 4.0, 4.01
When version 4.0 or 4.01 of CodeView for Windows is used to debug multiple applications simultaneously, and the user uses the Windows Task List application to activate application being debugged, CVW fails to stop execution on breakpoints in the activated application.
To avoid this problem, minimized the application currently being debugged before using the Windows Program Manager to activate the second application.
Note: Do not use the Windows Task List to activate the Program Manager. The Switch To option on the Windows system menu and the CTRL+ESC key combination access the Windows Task List.
Microsoft has confirmed this to be a problem in CodeView versions 4.0 and 4.01 for Windows. This problem was corrected in CodeView version 4.1 for Windows.
Page 380 of the Microsoft C/C++ "Environment and Tools" manual for version 7.0 details debugging multiple applications simultaneously.
The following nine steps reproduce the problem described above:
- In the Windows Program Manager, choose Run from the File menu.
In the Run dialog box, enter the CVW command, then the /L option and the name of the second applicatoin to debug, followed by the name of the first application to debug, as follows:
cvw /LSECOND.EXE FIRST.EXE
- In CodeView for Windows, choose Open Module from the File menu.
- In the Open Module dialog box, enter the name source module for the second application (for example, SECOND.C).
- Set a breakpoint anywhere in the second application.
- Press the F5 key to execute the first application.
- After the first application completes execution, use the Task List to activate the Program Manager. To use the Task list, choose the Switch To option from the Windows system menu or use the CTRL+ESC key combination.
- In the Program Manager, choose Run from the File menu.
- In the Run dialog box, enter the name of the second application.
Execution does not stop at the breakpoint set in the second application.
If the user does not use the Task List to activate the Program Manager (in other words, the user clicks on the Program Manager with the mouse), execution will halt at the breakpoint.
Additional query words: 4.00
Keywords : kb16bitonly
Issue type :
Technology : kbAudDeveloper kbCodeView kbCodeView400 kbCodeView401
Last Reviewed: June 26, 2001