Sure. I will post the output as soon as possible.
On Nov 25, 2014 8:27 PM, “Scott Noone” wrote:
>
>
>
> The TMF has to match the version of the Framework. Also, the TMFs are
distributed with the WDK, not with the WinDbg installation. Interestingly,
even though the v1.11 TMF was in the 8.0 WDK it has been removed from the
8.1 WDK (older Framework TMFs still exist though).
>
> However, starting with 1.11 the !wdflogdump command should automatically
extract the TMF from the Framework’s PDB. Can you post the unedited output
of !wdflogdump? You should see something like this:
>
> 0: kd> !wdfkd.wdfldr
> …
> LIBRARY_MODULE 0x84d03f60
> Version v1.11
> …
> 0: kd> !wdflogdump umbus.sys
> Trace searchpath is:
>
> Trace format prefix is: %7!u!: %!FUNC! -
> Trying to extract TMF information from -
f:\websymbols\Wdf01000.pdb\DC88E2E42C694181AA0C17FAFEC4C5B22\Wdf01000.pdb
> Log at 0x857ad000
> Gather log: Please wait, this may take a moment (reading 4032 bytes).
> % read so far … 10, 20, 30, 40, 50, 60, 70, 80, 100
> There are 80 log entries
> — start of log —
> 1: FxIFRStart - FxIFR logging started
>
> -scott
> OSR
> @OSRDrivers
>
>
> wrote in message news:xxxxx@ntdev…
>
>
> Tim,
>
> The SerialEvtIoDeviceControl handler receives a handle to WDFREQUEST and
WDFQUEUE objects. I am retrieving WDFDEVICE handle from WDFQUEUE object by
calling WdfIoQueueGetDevice() call. Then i am passing the handle to the
function WdfDeviceOpenRegistryKey() via multiple functions. I am not dong
anything with WDFDEVICE object in any of the intermediate functions before
i call WdfDeviceOpenRegistryKey() function.
>
> I hope passing a WDFDEVICE across functions is safe.
>
> Scott,
>
> I try to run the WDFLOGDUMP command i see the output as below. I am
pasting only a couple of entries because all other are identical.
>
> Unknown( 14): GUID=31f474a8-23f3-c270-e156-7b455a6f635c (No Format
> Information found).
> Unknown( 14): GUID=31f474a8-23f3-c270-e156-7b455a6f635c (No Format
> Information found).
> … and so on…
> … and so on…
> … and so on…
> ---- end of log ----
>
> This issue has been troubling me since very long.
>
> My target machine is running KMDF version 1.11. (i determined it by
running Wdfverifier.exe on the target machine) and the target machine is
running Win 7 embedded standard. I couldn’t find the appropriate .tmf file
for the kmdf version 1.11 in my windbg installation. I tried with
Wdf01009.tmf and above the output i got
>
> As per MSDN i don’t need to set the tmf file version if i am using KMDF
1.11 and a kernel debugger from Windows 8 or later. But since i am using
Windows 7 i thought i have to set the tmf file. But i need to know what the
.tmf file for KMDF 1.11.
>
>
> COuld it be related to incorrect symbols? My internet connection was
blocking some symbols so went to another target machine whose internet
connection is proper and downloaded symbols from the internet. I copied
those symbols onto my machine and using those symbols. I also specified the
microsoft symbol server path in Windbg along with the path of the copied
symbols. Could this excercise be incorrect and causing some problems?
>
> How to know what the appropriate .tmf file for my case and from where to
find it?
>
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer