Cannot start debuging

Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Cannot start debuging

Log In Register Lost Password
Viewing 6 posts - 16 through 21 (of 21 total)
1 2
  • Author
    Posts
  • May 31, 2011 at 16:25 #1745
    support
    Keymaster

    OK. That explains. To debug your driver you need either another physical PC, or a virtual machine.
    The easiest way is to install VirtualBox (it is free), install Windows into it, setup the VirtualKD back-end (go to http://visualddk.sysprogs.org/, look for vminstall), reboot your VM in debug mode and select it in the “Virtual Machine” combo box.

    May 31, 2011 at 17:21 #1746
    Saman
    Participant

    But I want debug on a second machine and IP adress at Target machine field is adress of the second machine,so how I must set Debug launch dialog for debugging on a second machine?

    May 31, 2011 at 17:24 #1747
    support
    Keymaster

    In order to debug a driver on a second machine, you either need either a direct COM, or FireWire connection. This is a general limitation related to driver debugging and is not VisualDDK-specific.

    May 31, 2011 at 20:26 #1748
    Saman
    Participant

    Hmm, I thought it may be also over network, and what is needed IP adress

    June 1, 2011 at 11:04 #1749
    support
    Keymaster

    The IP address is needed to control the driver and update its binary automatically. Otherwise, you would have to copy the file and start the service manually.

    June 22, 2011 at 16:38 #1760
    Anonymous
    Participant

    Thank you so much for this thread, it saved me a lot of time. I didn’t have the virtual machine setup… 🙂

  • Author
    Posts
Log In Register Lost Password
Viewing 6 posts - 16 through 21 (of 21 total)
1 2
  • You must be logged in to reply to this topic.