Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Cannot start debugging
- This topic has 42 replies, 3 voices, and was last updated 12 years, 2 months ago by Anonymous.
-
AuthorPosts
-
June 29, 2011 at 20:33 #317AnonymousParticipant
Hi,
I am trying to build and debug a driver that performs registry callbacks and i’ve been trying to get Visual DDK to work. I’ve successfully installed it on my host machine and VM. Now, I’m just having some issues with using my source files and getting it to build and debug.
I load my own source files and put everything in the project folder. I also have a ‘sources’ file because I use the WinDDK build. Here is my sources file:
TARGETNAME = wlreg TARGETTYPE = DRIVER LINKER_FLAGS=$(LINKER_FLAGS) /IGNORE:4210 TARGETLIBS = $(DDK_LIB_PATH)ntoskrnl.lib $(DDK_LIB_PATH)wdmsec.lib INCLUDES = ..;....include; SOURCES = ..Capture.cpp ..Device.cpp ..Driver.cpp ..Filter.cpp ..MultiQueue.cpp ..Process.cpp ..BufferWriter.cpp FilterWin7.cpp
Do I have to do anything special in Visual Studio project properties to get it to build?
June 29, 2011 at 20:59 #1808supportKeymasterYou can either create a new “make project” so that Visual Studio will invoke “build”, or use VisualDDK project wizard and select “use existing files” to have the project created for you.
June 30, 2011 at 15:56 #1809jlam9012ParticipantI tried selecting ‘use existing files’ with the VisualDDK project wizard. Here is the build output:
1> Build started: Project: Driver1, Configuration: Debug Win32 1>Build started 6/30/2011 11:23:10 AM.
1>Build:
1> OACR monitor running already
1> path contains nonexistant c:program files (x86)microsoft visual studio 10.0common7toolsbin, removing
1> BUILD: Compile and Link for x86
1>
1> BUILD: Loading c:winddk7600.16385.1build.dat...
1>
1> BUILD: Computing Include file dependencies:
1>
1> BUILD: Start time: Thu Jun 30 11:23:10 2011
1> BUILD: Saving c:winddk7600.16385.1build.dat...
1>
1> BUILD: Finish time: Thu Jun 30 11:23:11 2011
1> BUILD: Done
1>
1>
1>
1> 0 files compiled - 1 Warning
1>
1>
1>Build succeeded.
1>
1>Time Elapsed 00:00:01.14
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
June 30, 2011 at 16:01 #1810jlam9012ParticipantI tried selecting “use existing files” in the VisualDDK Project Wizard and got this build output:
1> Build started: Project: Driver1, Configuration: Debug Win32 1>Build started 6/30/2011 11:23:10 AM.
1>Build:
1> OACR monitor running already
1> path contains nonexistant c:program files (x86)microsoft visual studio 10.0common7toolsbin, removing
1> BUILD: Compile and Link for x86
1>
1> BUILD: Loading c:winddk7600.16385.1build.dat...
1>
1> BUILD: Computing Include file dependencies:
1>
1> BUILD: Start time: Thu Jun 30 11:23:10 2011
1> BUILD: Saving c:winddk7600.16385.1build.dat...
1>
1> BUILD: Finish time: Thu Jun 30 11:23:11 2011
1> BUILD: Done
1>
1>
1>
1> 0 files compiled - 1 Warning
1>
1>
1>Build succeeded.
1>
1>Time Elapsed 00:00:01.14
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
June 30, 2011 at 22:19 #1811jlam9012ParticipantPlease disregard my last 2 posts. I was able to get the driver to successfully build in Visual studio – hooray!!
But now, it gives me the error
“VisualDDK: Cannot start debugging: One of the library files needed to run this application cannot be found.”
The driver does successfully build – all my source files compile and I get a .sys file.
Thanks
July 1, 2011 at 12:34 #1812supportKeymasterHi, try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe
July 1, 2011 at 18:14 #1813jlam9012Participant@bazis wrote:
Hi, try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe
I tried that but still getting same error 🙁
July 2, 2011 at 09:13 #1814supportKeymasterDid you install the 32-bit Debugging tools?
July 5, 2011 at 13:40 #1815jlam9012ParticipantOn the host machine or virtual machine?
July 5, 2011 at 14:36 #1816supportKeymasterhost machine
July 7, 2011 at 15:13 #1817jlam9012ParticipantYes, I have installed the 32 bit debugging tools for windows on the host machine
July 10, 2011 at 12:37 #1827supportKeymasterPlease download VisualDDK 1.5.4, select “register debug version of DDKDebugger.dll” in installer, run Visual Studio as administrator, attempt debugging and post the DDKDebugger.log file from VisualDDK directory here. The log file should contain problem details.
July 11, 2011 at 12:34 #1826jlam9012ParticipantDDKDebugger.log
Initializing MSDBG session…
Loading dbgtools DLLs from C:Program Files (x86)Debugging Tools for Windows (x86)…
Session initialized successfully.+ 0.000 [ 0 ms]: MSDbgSession::UpdateOutputMask()
Session status changed to 4
+ 0.015 [ 2840 ms]: BasicMSDbgSession::StartSession()July 11, 2011 at 12:37 #1824supportKeymasterOK, I am assuming the problem occurs because the launcher cannot find the compiled sys file. You can try experimenting with the launcher settings, or installing the driver manually and using the Debug->Attach dialog to attach to the target machine.
July 11, 2011 at 20:26 #1825jlam9012ParticipantOk, I changed the “Driver file path on the target machine” to where my driver is on the vm. My driver is named wlreg.sys but it keeps trying to find Driver1.sys (Driver1 is the name of my VS project). How can i get it to stop searching for Driver1.sys…do I have to change the VS project name to the name of my driver?
-
AuthorPosts
- You must be logged in to reply to this topic.