Vs2017 is driven by IP debugging (dual machine debugging)

Preface

I wrote a blog before , Yes, it is vs2017 Debug the driver on the virtual machine through the serial port , But I feel that serial port debugging is not as convenient as network port debugging , Write an article here Debug the driver through the network port Methods .

On how to install WDK、 How to write driver , There are a lot of tutorials on the Internet , And I seem to have written before ？ All in all VS2017 Write on 、 Configuring the driver is still very simple and convenient .

Text

Here we call it installed VS2017 The host of is Debugger （IP by 192.168.101.5）, The host running the drive on the virtual machine is called Debugged machine （IP by 192.168.123.128）

To ensure that both sides can mutually PING through , If it doesn't work, close the firewalls of both sides .

It is said to guarantee , Virtual machine is Win8 And above ？ I never tried. , But it's better to have a professional version of the system , I test myself win10 The home version is no good .

One 、 Debugged machine （ virtual machine ） Configuration of

1、 First , We need to execute the following commands on the debugged machine ,CMD With administrator privileges, run and execute the following commands （ Set debug mode , Set the debugging machine IP）

bcdedit /set {default} DEBUG ON
bcdedit /set TESTSIGNING ON
bcdedit /debug on

//hostip For debugging machine IP, Don't fill in virtual machine IP！port It is the network communication port ,key Divide the password with a dot

bcdedit /dbgsettings net hostip:192.168.101.5 port:50080 key:theprevious.keys.arenot.secure

// Check whether the configuration is correct through the following command
bcdedit /dbgsettings

2、 On the debugged machine （ Again, virtual machines ） Need to install WDK Test Target Tools , Be careful 32 Bit system and 64 The bit system should be equipped with debugging tools of the corresponding architecture , My tool path is

C:\Program Files (x86)\Windows Kits\10\Remote\x64

C:\Program Files (x86)\Windows Kits\10\Remote\x86

All in all , It's easy to find it with any search tool . 

3、 The configuration on the debugged machine is completed and installed WDK Test Target After the tool , Restart the system now .

Two 、 Debugger （ installed VS2017 host ） Configuration of

1、 To configure Debugged machine Information

 

 

 

 

2、 Attach to the kernel and debug

  Show connected It means success ！！！！！！

but You also need to do the following ！ Otherwise, the breakpoint cannot be set ！

stay connected After success You also need to click all interrupts , At this time, the virtual machine can no longer move

  I waited about 2 Minutes later , There is int 3 The breakpoint

  At this point, enter... On the command line    g It means to continue , enter

  After that, you can load the driver in the virtual machine , Debug the breakpoint in the source code ！

above ！

This article refers to the following articles , I wrote it after stepping on the pit ：

VS2017+WDK10 Driver compilation and debugging _ If there is no ly The blog of -CSDN Blog _vs2017 wdk