Click here to Skip to main content
13,094,732 members (96,976 online)
Rate this:
Please Sign up or sign in to vote.

Host Win7_x64, target VM Win7_x64 both on same physical machine.
Driver debugging using VS 2012 (Visual Studio Integrated Windows Debugger.)

Able to provisioning between Host and target using VS 2012 and WDK 8.0.

KmdfSmall driver given on msdn is properly able to install on target VM; showing into Device Manager as well on target VM, as posted in my last query.

when ever I'm pressing F5, 'Debugger Immediate Window' in VS 2012 also showing 'breakpoint hit' and as I mentioned earlier in my msg, return value of KdPrintEx is also correct i.e. STATUS_SUCCESS.

Do I missing some setting into VS 2012 to display the msg's of "KdPrintEx". Means why my KdPrintEx((DPFLTR_IHVDRIVER_ID, DPFLTR_INFO_LEVEL, "\n KmdfSmallEvtDeviceAdd has been called\n")) is not printing any msg's into 'Debugger Immediate Window'.

Posted 14-Jun-13 22:28pm
Amit KD450

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 3

Hey Solved!

changed the value of Component Filter Mask on target machine where driver has been installed to debug.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter.

Under this key, created a value with the name "IHVDRIVER" and Set the value of this key equal to the DWORD value 0x8".

I choose "IHVDRIVER" because in my KdPrintEx((DPFLTR_"IHVDRIVER"_ID, DPFLTR_INFO_LEVEL, "\n KmdfSmallEvtDeviceAdd has been called\n"))
And DWORD value 0x8 because Leveling.

For detail:

thanks you


This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web01 | 2.8.170813.1 | Last Updated 16 Jun 2013
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100