Due to work needs, we need to use winDbg to debug the driver, which has never been used before. Today, I learned a simple way to build an environment and record it for later viewing.
If I use machine A to debug the driver running on machine B
Install winDbg on machine A. This is directly downloaded from the Internet. Remember its path for easy selection later.
Install targetvminstall.exe in the attached VirtualKD-2.3.zip on machine B, double-click to create a channel to connect with machine A, and add debugging startup items. After restarting, the system can choose to enter the system directly or enter debugging model,
Run vmmon64.exe or vmmon.exe in the attached VirtualKD-2.3.zip on machine A, as the case may be, to connect with the channel created in machine B,
After running vmmon64.exe, select the debugger path, which is the debugger path, and select the path of winDbg.exe.
Click Run debugger, windbg will run
After machine B enters the system
select debug mode
Then it will block, and windbg shows connected
After entering here, enter g, the b machine will continue to start and enter the desktop
Then it is the normal debugging stage. At present, I have not mastered the ability to debug the driver, so I need to warm up first.