怎样在虚拟机中搞驱动(国外英语资料).docVIP

怎样在虚拟机中搞驱动(国外英语资料) Driver debugging is a system-level debugging, so debugging tools with WinDbg is the best option. Driver debugging normally requires two computers. One is driven debugging as a host and the other is driven by the target machine. Of course, if there are no more computers, we can install VMware simulation system debugging (virtual machine). Its just a high level of configuration for the computer. This article describes the specific Settings and methods for debugging with WinDbg and WMware. This information is difficult to find on the Internet, and I have learned from other peoples valuable opinions to discuss. VMware Support said that WinDbg, since version , supported debugging through the pipe, but Microsoft didnt say anything about it. So, virtualized and debugged systems in VMware, and then through VMware virtual a com port. With this virtual port, you can debug with WinDbg. To download the latest version of the WinDbg tool, it is recommended that you use WinDbg with version 6.0 as a debugging tool. WMware can also be found on the site, but its better to use a high version. The installation process is simple, and you wont do much of this. The only thing to note is that after installing the virtual machine, select Install VM Tools... in the VMware master menu VM. Complete the installation of the system driver file. After installing these two software, install the same operating system as your computer version in VMware. For example: your computer is installed with Windows xp Professional, so its best to install the same version in Vmware. At least the same system, Windows XP? A Windows XP, Windows 2000? A Windows 2000. This avoids unnecessary problems in the drive debugging process. The operating system I used was Windows XP Professional. Run VMware, click Edit virtual machine Settings Click Add... To run VMware Select Serial Port, next Select Output to named pipe and click next The first box keeps the default \ \.\ pipe \ com_1 In the second box,