Tech Support > Microsoft Windows > Drivers > NOT working - KdPrintEx(( DPFLTR_IHVDRIVER_ID, flags,...
NOT working - KdPrintEx(( DPFLTR_IHVDRIVER_ID, flags,...
Posted by alex on October 4th, 2007



HI all,

KdPrintEx(( DPFLTR_IHVDRIVER_ID, 0x1,"test"));

does NOT show anything in windbg, even if i set
Kd_IHVDRIVER_Mask = 0x0FFF FFFF

target is xp-sp2 free build. Driver built using build 6000 DDK for XP
checked

any clues?

thanks
alex

Posted by Gabe on October 4th, 2007


On Oct 4, 11:18 am, alex <alex35...@yahoo.com> wrote:
I don't know if this will work, but maybe setting Kd_DEFAULT_Mask to
something like 0xf might help. I don't know if the default mask acts
as a sort of "global" mask or something

gabe


Posted by alex on October 6th, 2007


I also remember using this flag in my previous project months ago, but
surprisingly I dont see this flag now!!

In windbg the command

x nt!kd_default_mask

does not show anything. But I could see other flags like

549a4 nt!Kd_IHVSTREAMING_Mask = <no type information>
80554994 nt!Kd_IHVDRIVER_Mask = <no type information>
80554998 nt!Kd_IHVVIDEO_Mask = <no type information>
805549a0 nt!Kd_IHVNETWORK_Mask = <no type information>
805549a8 nt!Kd_IHVBUS_Mask = <no type information>
8055499c nt!Kd_IHVAUDIO_Mask = <no type information>

My target is NOT checked build, but XP-SP2 FREE build version running.
I dont think this should matter, does it ?

thx
alex



On Oct 4, 11:35 am, Gabe <gabe.bl...@ni.com> wrote:


Posted by Gabe on October 11th, 2007



Woops, I'm sorry, I should have read the post better. I think that
flag is a global mask on Vista only. From the KdPrintEx
documentation:

"KdPrintEx is identical to the DbgPrintEx routine in code that is
compiled in a checked build environment. This routine has no effect if
compiled in a free build environment. Only kernel-mode drivers can
call the KdPrintEx routine."

You may have already done this, but I'd double check and make sure you
are building in a checked build environment, otherwise, no print will
show up.


Posted by fedotov.alex@gmail.com on October 12th, 2007


alex wrote:

There is a problem with how DPFLTR_IHVDRIVER_ID is defined in the WDK.
See

http://www.osronline.com/showThread.cfm?link=107386

-- Alex Fedotov



Similar Posts