2.6 Debugging a Driver

You can debug the driver by using one of the following debugging tools.

Tool When Used

CodeViewÒ for Windows (CVW) Used mainly for debugging drivers written in the C language. CVW requires appropriate hardware, such as a secondary monitor, as well as appropriate compiler and link options to generate symbolic information.
WDEB386 Used for debugging drivers written in the assembly language. WDEB386 is required for debugging virtual devices in 386 enhanced mode. Despite its name, WDEB386 can be used with the 80286, 80386, or 80486 processor.

WDEB386 uses the first serial port (COM1) for all debugging input and output. This means you must connect a terminal (or a computer running terminal software) to COM1. WDEB386 sends and receives data according to the following communications specifications:

9600 baud rate

No parity

8 bits per character

1 stop bit

Specify symbol files for the driver you intend to debug, and any drivers or sys-tem modules that the driver may call. The symbol files contain the information WDEB386 needs to display the names of the functions, variables, and constants in the driver.