KMDF windbg !wdflogdump gives "could not retrieve WDF IFR header"

I'm developing with WDK 6001 (KMDF Version 1.7), and test
my driver under Vista32.
Under windbg, !wdflogdump shows only this:

-------- begin output -----------------
Using default driver name "<mydriver>"
Trace searchpath is:

Trace format prefix is: %7!u!: %!FUNC! -
TMF file used for formatting IFR log is:
<mypath>\wdf01007.tmf
error: Could not retrieve WDF IFR log header for driver <mydriver>.
hint: Build your driver with newer WDF libraries.
------------ end output --------------------

Here (http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx)
I found some (out dated) hints:
- I should add the DDK/WDK Symbol path ...
but I did'nt found it in the WDK 6001.
- I should load the correct wdfkd.dll ...
but "!load c:\WinDDK\6001.18000\bin\x86\wdfkd.dll" did not help.

I checked my Microsoft symserver cache, there I find only a
"wdf01000.pdb" ... I expected a wdf01005.pdb or wdf01007.pdb.

I assume it is a mismatch between Vista KMDF Version and WDK 6001, but I
may be wrong.


Thanks for helping !


J. Hoppe, PEAK-System Technik GmbH

Doron
Thu Mar 20 17:14:12 CDT 2008

are symbols for your driver loaded? what is the output of !lmi <mydriver>?

wdf01000.sys is for all v1.* versions of kdmf. v1.5 is still wdf01000.sys
as is v1.7.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Joerg Hoppe" <jhoppe@community.nospam> wrote in message
news:%23ttXLMniIHA.3780@TK2MSFTNGP06.phx.gbl...
> I'm developing with WDK 6001 (KMDF Version 1.7), and test
> my driver under Vista32.
> Under windbg, !wdflogdump shows only this:
>
> -------- begin output -----------------
> Using default driver name "<mydriver>"
> Trace searchpath is:
>
> Trace format prefix is: %7!u!: %!FUNC! -
> TMF file used for formatting IFR log is:
> <mypath>\wdf01007.tmf
> error: Could not retrieve WDF IFR log header for driver <mydriver>.
> hint: Build your driver with newer WDF libraries.
> ------------ end output --------------------
>
> Here (http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx)
> I found some (out dated) hints:
> - I should add the DDK/WDK Symbol path ...
> but I did'nt found it in the WDK 6001.
> - I should load the correct wdfkd.dll ...
> but "!load c:\WinDDK\6001.18000\bin\x86\wdfkd.dll" did not help.
>
> I checked my Microsoft symserver cache, there I find only a
> "wdf01000.pdb" ... I expected a wdf01005.pdb or wdf01007.pdb.
>
> I assume it is a mismatch between Vista KMDF Version and WDK 6001, but I
> may be wrong.
>
>
> Thanks for helping !
>
>
> J. Hoppe, PEAK-System Technik GmbH

Joerg
Tue Mar 25 04:06:17 CDT 2008

Doron Holan [MSFT] schrieb:
> are symbols for your driver loaded? what is the output of !lmi <mydriver>?
>
> wdf01000.sys is for all v1.* versions of kdmf. v1.5 is still
> wdf01000.sys as is v1.7.
>
> d
>
<mydriver> is "dspace_usb"

This is the error:
-------- windbg begin ----------------
1: kd> !wdflogdump
Using default driver name "DSPACE_USB2"
Trace searchpath is:

Trace format prefix is: %7!u!: %!FUNC! -
TMF file used for formatting IFR log is:
T:\driver\PEAKCAN3\DSPACE_USB2\OBJCHK_WXP_x86\i386\debug\wdf01007.tmf
error: Could not retrieve WDF IFR log header for driver DSPACE_USB2.
hint: Build your driver with newer WDF libraries.
-------- windbg end ----------------



Symbols seem fine:
-------- windbg begin ----------------
1: kd> !lmi dspace_usb2
Loaded Module Info: [dspace_usb2]
Module: DSPACE_USB2
Base Address: 9b00f000
Image Name: DSPACE_USB2.SYS
Machine Type: 332 (I386)
Time Stamp: 47e22d4e Thu Mar 20 10:24:30 2008
Size: 4ed00
CheckSum: 50c1c
Characteristics: 102
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 66, 225a8, 225a8 RSDS - GUID:
{2EBE8FA5-F172-4CC4-80DA-A18B7092C803}
Age: 1, Pdb:
d:\peak\peakcan3\source_build\dspace_usb2\objchk_wxp_x86\i386\DSPACE_USB2.pdb
Image Type: MEMORY - Image read successfully from loaded memory.
Symbol Type: PDB - Symbols loaded successfully from symbol
search path.

T:\driver\PEAKCAN3\DSPACE_USB2\OBJCHK_WXP_x86\i386\symbols\DSPACE_USB2.pdb
Compiler: Resource - front end [0.0 bld 0] - back end [8.0 bld
50727]
Load Report: private symbols & lines, not source indexed

T:\driver\PEAKCAN3\DSPACE_USB2\OBJCHK_WXP_x86\i386\symbols\DSPACE_USB2.pdb
-------- windbg end ----------------

Doron
Tue Mar 25 15:47:45 CDT 2008

the TMF file you need to use is
<ddkroot>\6001.18000\tools\tracing\i386\wdf01007.tmf, not sure how that file
got into your obj path. The v1.7 installer is not yet out, are you using
the released wdk or a pre release version?

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Joerg Hoppe" <jhoppe@community.nospam> wrote in message
news:OeDlueljIHA.1164@TK2MSFTNGP02.phx.gbl...
> Doron Holan [MSFT] schrieb:
>> are symbols for your driver loaded? what is the output of !lmi
>> <mydriver>?
>>
>> wdf01000.sys is for all v1.* versions of kdmf. v1.5 is still
>> wdf01000.sys as is v1.7.
>>
>> d
>>
> <mydriver> is "dspace_usb"
>
> This is the error:
> -------- windbg begin ----------------
> 1: kd> !wdflogdump
> Using default driver name "DSPACE_USB2"
> Trace searchpath is:
>
> Trace format prefix is: %7!u!: %!FUNC! -
> TMF file used for formatting IFR log is:
> T:\driver\PEAKCAN3\DSPACE_USB2\OBJCHK_WXP_x86\i386\debug\wdf01007.tmf
> error: Could not retrieve WDF IFR log header for driver DSPACE_USB2.
> hint: Build your driver with newer WDF libraries.
> -------- windbg end ----------------
>
>
>
> Symbols seem fine:
> -------- windbg begin ----------------
> 1: kd> !lmi dspace_usb2
> Loaded Module Info: [dspace_usb2]
> Module: DSPACE_USB2
> Base Address: 9b00f000
> Image Name: DSPACE_USB2.SYS
> Machine Type: 332 (I386)
> Time Stamp: 47e22d4e Thu Mar 20 10:24:30 2008
> Size: 4ed00
> CheckSum: 50c1c
> Characteristics: 102
> Debug Data Dirs: Type Size VA Pointer
> CODEVIEW 66, 225a8, 225a8 RSDS - GUID:
> {2EBE8FA5-F172-4CC4-80DA-A18B7092C803}
> Age: 1, Pdb:
> d:\peak\peakcan3\source_build\dspace_usb2\objchk_wxp_x86\i386\DSPACE_USB2.pdb
> Image Type: MEMORY - Image read successfully from loaded memory.
> Symbol Type: PDB - Symbols loaded successfully from symbol search
> path.
>
> T:\driver\PEAKCAN3\DSPACE_USB2\OBJCHK_WXP_x86\i386\symbols\DSPACE_USB2.pdb
> Compiler: Resource - front end [0.0 bld 0] - back end [8.0 bld
> 50727]
> Load Report: private symbols & lines, not source indexed
>
> T:\driver\PEAKCAN3\DSPACE_USB2\OBJCHK_WXP_x86\i386\symbols\DSPACE_USB2.pdb
> -------- windbg end ----------------

Joerg
Wed Mar 26 02:30:31 CDT 2008

Doron Holan [MSFT] schrieb:
> the TMF file you need to use is
> <ddkroot>\6001.18000\tools\tracing\i386\wdf01007.tmf, not sure how that
> file got into your obj path. The v1.7 installer is not yet out, are you
> using the released wdk or a pre release version?
>
Doron,

- My wdf1007.tmf is copied from C:\WinDDK\6001.18000\tools\tracing\i386\

- I believe the Installer to be
c:\WinDDK\6001.18000\redist\wdf\x86\WdfCoInstaller01007.dll,
but if its not yet out, then which file do I have to care for?

joerg

Joerg
Wed Mar 26 04:14:07 CDT 2008

Doron Holan [MSFT] schrieb:
> the TMF file you need to use is
> <ddkroot>\6001.18000\tools\tracing\i386\wdf01007.tmf, not sure how that
> file got into your obj path. The v1.7 installer is not yet out, are you
> using the released wdk or a pre release version?
>
Doron,

Perhaps I found the solution:
I disabled loading of unqualified symbols.
.symopt+ 0x100
It seems that this is the problem, I will investigate further.

I've done this because symbol loading was incredible sloooow.

So next question: How can I speed up symbol loading when I have to use
.symopt- 0x100
?

Joerg

Doron
Wed Mar 26 15:34:52 CDT 2008

well, the KMDF extensions use unqualified symbol names b/c the version of
KMDF can be different across releases while the extension stays the same.
do you have a cache setup for symbols in your sympath? that helps
tremendously

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Joerg Hoppe" <jhoppe@community.nospam> wrote in message
news:u%23tTyHyjIHA.6092@TK2MSFTNGP06.phx.gbl...
> Doron Holan [MSFT] schrieb:
>> the TMF file you need to use is
>> <ddkroot>\6001.18000\tools\tracing\i386\wdf01007.tmf, not sure how that
>> file got into your obj path. The v1.7 installer is not yet out, are you
>> using the released wdk or a pre release version?
>>
> Doron,
>
> Perhaps I found the solution:
> I disabled loading of unqualified symbols.
> .symopt+ 0x100
> It seems that this is the problem, I will investigate further.
>
> I've done this because symbol loading was incredible sloooow.
>
> So next question: How can I speed up symbol loading when I have to use
> .symopt- 0x100
> ?
>
> Joerg
>