Prev: WDK for build 5600
Next: NTStatus codes missing
From: PRANAV KANT GAUR on 24 Mar 2010 07:27
I have tried to read the log maintained by kmdf for my driver using:
!c:\winddk\6000\x86\bin\wdfkd.wdflogdump <drivername>
command in Windbg,but it responds as:

Trace searchpath is:

Trace format prefix is: %7!u!: %!FUNC! -
TMF file used for formatting IFR log is:
c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
hint: Are symbols available for this driver?
hint: Did you exclude the .sys extension in the drivername parameter?

Could not find c:\users\parnav\desktop\test\mytestdriver in wdfldr client list

where 'c:\users\parnav\desktop\test\' is path for my driver that i specified
as parameter to 'wdflogdump' routine.
driver image name:mytestdriver
Wdk version:6000

what is 'wdfldr client list' here & how i can modify it to add my driver to
it ?
From: Egidio [MSFT] on 24 Mar 2010 10:35
if you run !wdfldr you will see the list of wdf drivers, your driver should
be already listed there.
When you run !wdflogdump don't need to include the path name.

Egi.

"PRANAV KANT GAUR" <PRANAVKANTGAUR(a)discussions.microsoft.com> wrote in
message news:83F093B6-84B8-474D-AED2-C0B55D41156D(a)microsoft.com...
> I have tried to read the log maintained by kmdf for my driver using:
> !c:\winddk\6000\x86\bin\wdfkd.wdflogdump <drivername>
> command in Windbg,but it responds as:
>
> Trace searchpath is:
>
> Trace format prefix is: %7!u!: %!FUNC! -
> TMF file used for formatting IFR log is:
> c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
> hint: Are symbols available for this driver?
> hint: Did you exclude the .sys extension in the drivername parameter?
>
> Could not find c:\users\parnav\desktop\test\mytestdriver in wdfldr client
> list
>
> where 'c:\users\parnav\desktop\test\' is path for my driver that i
> specified
> as parameter to 'wdflogdump' routine.
> driver image name:mytestdriver
> Wdk version:6000
>
> what is 'wdfldr client list' here & how i can modify it to add my driver
> to
> it ?

From: Tim Roberts on 24 Mar 2010 23:57
PRANAV KANT GAUR <PRANAVKANTGAUR(a)discussions.microsoft.com> wrote:

>I have tried to read the log maintained by kmdf for my driver using:
>!c:\winddk\6000\x86\bin\wdfkd.wdflogdump <drivername>
>command in Windbg,but it responds as:
>
>Trace searchpath is:
>
>Trace format prefix is: %7!u!: %!FUNC! -
>TMF file used for formatting IFR log is:
>c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
>hint: Are symbols available for this driver?
>hint: Did you exclude the .sys extension in the drivername parameter?
>
>Could not find c:\users\parnav\desktop\test\mytestdriver in wdfldr client list
>
>where 'c:\users\parnav\desktop\test\' is path for my driver that i specified
>as parameter to 'wdflogdump' routine.
>driver image name:mytestdriver
>Wdk version:6000

Did you really specify the whole path in the wdflogdump command? Where did
you get the idea that you needed that?

!load wdfkd
!wdftmffile c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
!wdflogdump mytestdriver

That's all you need.

Also, based on the path you provided, I'm going to guess that you are
running Windows 7. In that case, you aren't really using wdf01005, you are
using wdf01009, and you must use that TMF file. For that, you'll need the
7600 WDK.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: PRANAV KANT GAUR on 25 Mar 2010 09:36


"Tim Roberts" wrote:

> PRANAV KANT GAUR <PRANAVKANTGAUR(a)discussions.microsoft.com> wrote:
>
> >I have tried to read the log maintained by kmdf for my driver using:
> >!c:\winddk\6000\x86\bin\wdfkd.wdflogdump <drivername>
> >command in Windbg,but it responds as:
> >
> >Trace searchpath is:
> >
> >Trace format prefix is: %7!u!: %!FUNC! -
> >TMF file used for formatting IFR log is:
> >c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
> >hint: Are symbols available for this driver?
> >hint: Did you exclude the .sys extension in the drivername parameter?
> >
> >Could not find c:\users\parnav\desktop\test\mytestdriver in wdfldr client list
> >
> >where 'c:\users\parnav\desktop\test\' is path for my driver that i specified
> >as parameter to 'wdflogdump' routine.
> >driver image name:mytestdriver
> >Wdk version:6000
>
> Did you really specify the whole path in the wdflogdump command? Where did
> you get the idea that you needed that?
>
> !load wdfkd
> !wdftmffile c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
> !wdflogdump mytestdriver
>
> That's all you need.
>
> Also, based on the path you provided, I'm going to guess that you are
> running Windows 7. In that case, you aren't really using wdf01005, you are
> using wdf01009, and you must use that TMF file. For that, you'll need the
> 7600 WDK.
> --
> Tim Roberts, timr(a)probo.com
> Providenza & Boekelheide, Inc.
> .
> I have tried the steps that you suggested but it still gives message:
Could not find mytestdriver in wdfldr client list

what is wdfldr client list & how can i add my driver in that list?

From: Egidio [MSFT] on 25 Mar 2010 11:44
You will not find your kmdf driver listed in !wdfldr if that driver has been
unloaded.
Set a bp in your code before your driver unloads and you should be able to
see it listed there.

Egi.

"PRANAV KANT GAUR" <PRANAVKANTGAUR(a)discussions.microsoft.com> wrote in
message news:1A2B718C-DBD4-4425-BF65-5B00A712D2E2(a)microsoft.com...
>
>
> "Tim Roberts" wrote:
>
>> PRANAV KANT GAUR <PRANAVKANTGAUR(a)discussions.microsoft.com> wrote:
>>
>> >I have tried to read the log maintained by kmdf for my driver using:
>> >!c:\winddk\6000\x86\bin\wdfkd.wdflogdump <drivername>
>> >command in Windbg,but it responds as:
>> >
>> >Trace searchpath is:
>> >
>> >Trace format prefix is: %7!u!: %!FUNC! -
>> >TMF file used for formatting IFR log is:
>> >c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
>> >hint: Are symbols available for this driver?
>> >hint: Did you exclude the .sys extension in the drivername parameter?
>> >
>> >Could not find c:\users\parnav\desktop\test\mytestdriver in wdfldr
>> >client list
>> >
>> >where 'c:\users\parnav\desktop\test\' is path for my driver that i
>> >specified
>> >as parameter to 'wdflogdump' routine.
>> >driver image name:mytestdriver
>> >Wdk version:6000
>>
>> Did you really specify the whole path in the wdflogdump command? Where
>> did
>> you get the idea that you needed that?
>>
>> !load wdfkd
>> !wdftmffile c:\winddk\6000\tools\tracing\i386\wdf01005.tmf
>> !wdflogdump mytestdriver
>>
>> That's all you need.
>>
>> Also, based on the path you provided, I'm going to guess that you are
>> running Windows 7. In that case, you aren't really using wdf01005, you
>> are
>> using wdf01009, and you must use that TMF file. For that, you'll need
>> the
>> 7600 WDK.
>> --
>> Tim Roberts, timr(a)probo.com
>> Providenza & Boekelheide, Inc.
>> .
>> I have tried the steps that you suggested but it still gives message:
> Could not find mytestdriver in wdfldr client list
>
> what is wdfldr client list & how can i add my driver in that list?
>
 | 
Pages: 1
Prev: WDK for build 5600
Next: NTStatus codes missing