|
|
Home  Connectivity Software
Support
WinDriver Support
Technical Documents
Technical Document #12
| Doc ID: |
12 |
| Product: |
WinDriver & KernelDriver |
| Version: |
-- |
What is the Debug Monitor utility and how can I use it?
|
WinDriver's Debug Monitor - wddebug_gui (found in the WinDriver/util directory) - is a GUI application program that logs detailed debugging information from the WinDriver kernel. (For a description of the non-graphical wddebug utility, please refer to Technical Document #13 - for Windows CE, Linux and Solaris, and Technical Document #14 - for VxWorks). A detailed description of the Debug Monitor utility can be found in the WinDriver User's Manual.
To start the graphical Debug Monitor utility, do one of the following:
- Run wddebug_gui from the WinDriver/util (or KernelDriver/util) directory.
- From the DriverWizard select: Tools-> Debug Monitor.
- On Windows platforms, you can run the program from the Start-up menu:
Start --> Programs --> WinDriver(/KernelDriver)
--> Debug Monitor (or: Monitor Debug Messages - in version 5.05b or earlier of WinDriver/KernelDriver).
When the debug Monitor starts, it prints the following message:
-------------------------------------------------------
WinDriver Debugging Monitor ‹Program Version Number›.
Running WinDriver ‹WinDriver Kernel Version Number› Jungo (c)‹Year› Build
Date:‹Build Date› ‹CPU› ‹SYS\VXD›
Time: ‹Time & Date›
OS: ‹OS details›
-------------------------------------------------------
The debug messages follow after this whenever you perform an operation with WinDriver. When sending the debug messages to the Jungo support personnel, please do not delete the initial driver and system information from the Debug Monitor window.
Trace mode implies that the maximum level of debugging information will be logged. To set the debug level to 'Trace' mode, invoke View --> Debug Options from the Debug Monitor Menu and then click on the check item labeled 'Trace' in the 'Level' section.
When reporting a problem, run the Debug Monitor, set the debug level to 'Trace', leave the debug window open, run your application, reproduce the problem and then send us the entire output of the debug log.
Please observe the lines in the Debug Monitor around where your problem occurs and insert a remark there for our support personnel.
If the problem was encountered when running your application on a target machine, on which WinDriver is not installed, you can copy the wddebug_gui program to this machine and run it directly on the target as well.
You can also use the WD_DebugAdd() function to send your own debug messages from the code to the debug log. This function is available from version 5.03 of WinDriver and described in the Function Reference chapter of the WinDriver User's Manual. Please note that this function can be called from both a user-mode and a kernel-mode application, and can even be called from within the Kernel PlugIn KP_IntAtIrql() function, which is executed at HIGH IRQL.
Please also refer to Technical Document #44 for an explanation regarding the possibility of sending the debug messages from the Debug Monitor to a kernel debugger.
Back to Top
|
|
