DebugView is an application that lets you monitor debug output on your local system, or any computer on the network that
you can reach via TCP/IP. It can display both kernel-mode and Win32 debug output generated by standard debug print APIs.
DebugView works on Windows 95, 98, Me, NT 4, 2000, XP and .NET Server.
DebugView can be downloaded from:
http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx
DebugView Uses in WinDriver and KernelDriver:
- When using the Debug Monitor application, you can select the Send debug messages to the operating system kernel debugger checkbox if you want debugging messages to be sent to an external kernel debugger (DebugView, for example). This option enables you to send to an external kernel debugger all the debug information that is received by the Debug Monitor. The debug information can be of two major types: messages sent to the Debug Monitor automatically from WinDriver's kernel module or messages sent from the code to the Debug Monitor using WD_DebugAdd().
After selecting the check box, run your application, reproduce the problem, and view the debug information in the external kernel debugger’s log (in DebugView). For more information regarding this option, refer to Technical Document 44.
- The skeletal USB driver code in KernelDriver includes a user-mode project. The output of the user-mode project is a diagnostics application, xxx_diag.exe, which prints the device configuration to the Kernel Debugger (DebugView, for example), and demonstrates how to perform a data transfer (read from or write to the device).
- Interrupt handling using KernelDriver involves a step in which when an interrupt is received from the hardware, a callback function is called, and sends debug printouts to the kernel debugger (DebugView, for example).
Back to Top
|
