tracedmp [options] | [-h | -?]tracedmp [options] | [-h | -?]
Where:
Dumpfile.csv
This file contains a count of all the events that occurred while tracing was being performed. The GUIDs for each event is also displayed. It is important to understand the difference between Event type (start/end) and Event type (DCstart/DCend (DC stands for Data Collection)). The former are those events that started and ended after tracing had begun. They had their lifetime within the tracing period.
There are processes or threads that began before tracing had been turned on, and will continue even after tracing is completed. For such events, the tool recognizes their start as the time tracing was turned on, and their end as the time tracing was turned off. This is the definition of DCstart and DCend.
This file can be opened in Microsoft® Excel. It contains a list of the events as they occurred in chronological order. The various fields are:
| Event name | Name of the event being traced |
|---|---|
| TID | Thread ID |
| Clock-time | The timestamp of the event occurrence. |
| Kernel (ms) | Time taken by that event in the kernel space. |
| User (ms) | Time taken by the event in the user space. |
| User data | The variable portion of the header. Based on the MOF structure provided in the MOFdata.guid file. This could be more than one column of data. To interpret, look in the Mofdata.guid file or run WEBMTest. |
| IID | Instance ID |
| PIID | Parent Instance ID to which the IID relates. |
Note
IID and PIID are the last two columns (on the right) of the output file and should not be mistaken for User Data, as this field could span multiple columns.