Session export format - HTML or XML
-exportAsXML
Export the session data as an HTML or XML file when Memory Validator has finished collecting data from the target program.
Example:
-exportAsHTML c:\results\html\testMacro1.html
-exportAsXML "c:\test results\xml\testMacro1.html"
See also the section on XML Export Tags.
Session export encoding - HTML or XML
These options allow you to export the session data as UTF-16, UTF8 or ASCII. UTF-16 and UTF-8 will add a byte order mark (BOM) to the start of the exported file.
The exported HTML will be exported with the appropriate format.
-exportAsHTML_BOM ASCII
-exportAsHTML_BOM UTF8
-exportAsHTML_BOM UTF16
The exported XML will be exported with the appropriate format.
-exportAsXML_BOM ASCII
-exportAsXML_BOM UTF8
-exportAsXML_BOM UTF16
HTML and XML export options
The following options control settings for HTML and XML export of the recorded session results
All the export settings take the form option:On or Option:Off
Example:
-htmlAllocMemory:On
-xmlReAllocMemory:Off
All these options are equivalent to the settings used in the Export Session dialog.
-htmlAllocMemory -xmlAllocMemory |
Include allocated memory data in the export |
-htmlReAllocMemory -xmlReAllocMemory |
Include reallocated memory data in the export
|
-htmlFreeMemory -xmlFreeMemory |
Include free memory data in the export |
-htmlLeaksOnly -xmlLeaksOnly |
Only include information about leaked data |
-htmlMemory -xmlMemory |
Include data describing memory allocations |
-htmlMemoryStackTrace -xmlMemoryStackTrace |
Include stack traces for memory allocations |
-htmlMemoryFilter -xmlMemoryFilter |
Apply filters (session or global) to data memory allocations |
-htmlHandles -xmlHandles |
Include data describing handle allocations |
-htmlHandleStackTrace -xmlHandleStackTrace |
Include stack traces for handle allocations |
-htmlHandleFilter -xmlHandleFilter |
Apply filters (session or global) to data for handle allocations |
-htmlErrors -xmlErrors |
Include data describing error conditions |
-htmlErrorStackTrace -xmlErrorStackTrace |
Include stack traces for error conditions |
-htmlErrorFilter -xmlErrorFilter |
Apply filters (session or global) to data for error conditions |
-htmlTrace -xmlTrace |
Include data describing TRACE and OutputDebugString information |
-htmlTraceStackTrace -xmlTraceStackTrace |
Include stack traces for trace information |
-htmlTraceFilter -xmlTraceFilter |
Apply filters (session or global) to data for trace information |
-htmlDetailedReport -xmlDetailedReport |
Include Thread ID and Timestamp information as additional data |
Make the HTML export colour coded (not relevant for XML export) |
|
Use the old style (flat) XML report without the <EVENT> tag. See XML Export Tags. |
Exporting objects
Exporting data about objects doesn't correspond to any corresponding setting in the user interface.
When running automated regression tests in unattended mode, you won't be able to manually inspect the Types tab, so exporting this data can be very useful.
You can choose to export all the Objects data or just the data for leaked objects.
-exportSessionObjectsXML
Exports the data on the Types tab (sub tab "DLL", for all threads) as an HTML or XML file when Memory Validator has finished collecting data from the target program.
Example:
-exportSessionObjectsHTML c:\results\html\testMacro1Objects.html
-exportSessionObjectsHTML "c:\test results\xml\testMacro1Objects.html"
-exportSessionLeakedObjectsHTML
-exportSessionLeakedObjectsXML
As above, but only data for objects with a non-zero Count value is exported.
Since the Count column indicates live allocations a non-zero count indicates leaked objects once the target program has exited.
See also -filterSessionLeakedObjectsHTML / XML for applying global filters to exported session objects.
