Microsoft KB Archive/99183

{|
 * width="100%"|

PRB: No or Partial Output Debugging QuickWin Application

 * }

Q99183

1.00 1.50 1.51 1.52 WINDOWS kbtool kbprb - The information in this article applies to: - The Visual Workbench Integrated Debugger included with: - Microsoft Visual C++ for Windows, versions 1.0, 1.5, 1.51, and 1.52 - SYMPTOMS ======== When debugging a QuickWin application, the application produces either no output or only partial output. CAUSE ===== This error is caused by inherent problems with GUI-hosted debugging. During the debugging process, if the debugger window covers the application's output window, particularly when a breakpoint is hit or when single- stepping, the application may not redraw its output when it is activated. RESOLUTION ========== When debugging output from the application, make sure that the debugger and application windows do not overlap. This can be best accomplished by tiling the windows (activate the Task Manager and choose Tile). MORE INFORMATION ================ During the process of debugging a QuickWin application, you may lose output if the following conditions occur: - The application window is partially or completely covered by the debugger window. - The application reaches a breakpoint in the debugger and the user attempts to view the output of the application by bringing the application window to the front. When the application reaches a breakpoint, it does not receive any messages. Because each application in the Microsoft Windows environment receives WM_PAINT messages (including QuickWin applications for which support is built-in), this problem also manifests itself in other applications while debugging the WM_PAINT message processing itself. Additional reference words: 1.00 1.50 paint KBCategory: kbtool kbprb KBSubcategory: WBDebug

Keywords : kb16bitonly

Issue type :

Technology : kbVCsearch kbAudDeveloper