The information in this article applies to:
SUMMARY
The debugging version of Windows replaces the core Windows code with code
that provides additional error checking and reporting not in the standard
(non-debugging) version of Windows. This information is useful if you are a
developer testing your own application under Windows. The debugging version
of Windows will point you to resource leaks and errors that go otherwise
undetected; therefore, it is a good idea to run your application under the
debugging version at least once, even if the program appears to run without
any problems.
MORE INFORMATION
First, follow the guidelines in your manual to install the debugging
version of Windows. If you have already installed the SDK or Visual C++ and
did not choose to install the debugging version, run the setup program
again. You only have to install the debugging version at this point. The
debugging version is called the "debug kernel." The term "kernel" refers to
the operating system core. In Windows, the kernel consists of the GDI.EXE,
KRNL386.EXE, and USER.EXE files.
Q86263 Redirecting Debugging Information Under WindowsYou can control the level of diagnostic information by using the debugging version of Windows. The groups of output options are break options, debug options, and trace options. The debug option "break with INT 3" is useful if you are running your program under the debugger: when the program causes a general-protection (GP) fault, the debugger stops on the line of code where the fault occurred. In general, it is a good idea to check all of the trace options and also clear the "Print on Break Only" check box so that printing occurs synchronously. For more information on the debugging version of Windows and the debugging options, see the DBWIN.TXT file that is included with the DBWIN sample and the "Windows Debugging Version/Debugging Programs" topic in the SDK help file. You can use OutputDebugString() or DebugOutput() in your own application to print debugging output. These APIs are easier to use than MessageBox(). When you run the debugging version of Windows, you may notice errors from other Windows-based applications that you are running. Other applications can even cause general protection faults or machine hangs when they are run under the debugging version. This is a sign that the application developer did not test the application under the debugging version of Windows. If you have an application in your startup group that prevents the debugging version of Windows from loading, hold down the Shift key while booting so that the applications in your startup group are not started. Additional query words: 3.10
Keywords : kb16bitonly TlsDbgWin |
Last Reviewed: November 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |