none
WPA and TMF

All replies

  • I'm asking myself the exact same question too right now.

    I try to add some more details to it:

    When tracing a driver with WPP you can use .TMF files to link the raw tracing data to the human readable messages.

    You can link this data together with:

    tracefmt mylog.etl -p c:\tmffiles\ -o outdata.txt

    (and possibly some more parameters to it)

    in outdata.txt there is something like...

    EventTrace
    [0]0000.0000::03/26/2013-15:18:56.156.790700 [src]NICGetMediaConnectStatus
    [0]0000.0000::03/26/2013-15:18:56.856.821600 [src]NICGetMediaConnectStatus
    [0]0000.0000::03/26/2013-15:18:57.556.853200 [src]NICGetMediaConnectStatus
    [0]0000.0000::03/26/2013-15:18:58.255.886700 [src]NICGetMediaConnectStatus
    [0]0000.0000::03/26/2013-15:18:58.955.919400 [src]NICGetMediaConnectStatus
    [0]0000.0000::03/26/2013-15:18:59.655.952400 [src]NICGetMediaConnectStatus
    [1]0004.002C::03/26/2013-15:19:00.231.959100 [src]SendPackets BEGIN
    [1]0004.002C::03/26/2013-15:19:00.231.960100 [src]SendPackets Inbetween
    ...

    a textual representation is nice, but if you could use that data in XPerf or WPA (Windows Performance Analyzer) GUI, that would be great!

    But: How can i tell the GUIs to use the .tmh or .pdb data?

    XPerf or WPA do only show these diamond shaped dots on the timeline with no further information about the source of this event.

    • Edited by Dan.at Tuesday, March 26, 2013 3:06 PM added details
    Tuesday, March 26, 2013 2:49 PM
  • could eventually someone have a look at this?

    probably there is some flaw in the documentation about this issue, or is it just us two?

    Thursday, March 28, 2013 2:23 PM
  • Hi,

    its not just you two. :-)

    I am also very interested in a solution to this problem.

    Friday, March 29, 2013 7:44 AM
  • Me too... bother me for 2 days to find a solution.
    Friday, August 09, 2013 12:32 AM