Attached to process debugging

[Anonymous]

Hi all,

I’m new to driver development, and am trying to debug an intermediary network driver using VisualDDK (on VS2008). I’ve used the “attach to process” feature and managed to connect to the kernel level.

However, I am unable to put breakpoints on my project’s source code. It says that “The breakpoint will not curently be hit. No symbols have been loaded for this document.” I’ve manually copied the driver to ensure that the build version is the same as the symbols file. Am I supposed to provide the symbol path somewhere in the visualDDK settings like how i would in Windbg? Or there’s something else I should configure?

Thanks.

[echobravo]

So I have this exact question and would be happy to RTFM, but I have not found the manual…
I can attach to process (VM), but can’t load the source/symbols etc… you know – actually debug 😉

I already have an existing driver vcproj and I wanted to leverage VisualDDK & VirtualKD to debug on my VM.
Do I have to convert the vcproj in VisualDDK or something like that (not very desirable) OR can I simply set the SYMPATH?

Host: Win7x64, VMWare Workstation 7.1.2, WDK 6000, VS2008, VirtualKD 2.5.1, VisualDDK 1.5
Target/Guest: Win7x86

Thanks in advance,
EB

[Author]

Posts