Please enable JavaScript to view this site.

Memory Validator Help

 

 

Exporting to HTML or XML

 

Exporting sessions allows you to use external tools to analyse or view session data for whatever reasons you might need.

 

You can export to HTML or XML format:

 

menu File menu instructionStep Export Session... instructionStep Choose HTML Report or XML Report instructionStep shows the Export Session dialog below

 

 

Exporting is not saving

 

You can't import session data.

 

Use save and load if you want to save session data for loading back into Memory Validator at a later date.

 

 

The Export Session dialog

 

The Export Session dialog looks very similar to the Save Session dialog, except there are more options enabled.

 

export-session-dialog

 

 

Memory or Objects

 

Choose to export object data or memory data:

 

Objects Report instructionStep will export a set of data corresponding to the Objects tab view
 

Memory Report instructionStep will export memory allocations, types, callstacks etc

 

An Objects Report will disable all the other options apart from the File settings.

 

If exporting a memory report, choose the options in the Scope, Type and Extra Information sections:

 

 

Scope section

 

Allocated Memory instructionStep all memory and resource allocations not deallocated and information about damaged memory

 

Reallocated Memory instructionStep all allocations that have been reallocated

 

Free Memory instructionStep all allocations that have been deallocated

 

Only Export Leaked Data instructionStep check to export memory known to have leaked

 

Useful if using in-place leak detection during a session and want to export data before the session completes.

 

Type section

 

Choose what type of data you want to include

 

Memory instructionStep memory allocations, reallocations and deallocations

 

Handle instructionStep resource allocations and deallocations

 

Errors instructionStep error conditions such as damaged memory, incorrect deallocation, uninitialized memory

 

Trace instructionStep TRACE() and OutputDebugString() messages

 

For each type of data

 

Include Stack Trace instructionStep includes the allocation stack trace information in the export

 

Filter instructionStep filters the exported data according to the global and the session filters

 

Leaving the export unfiltered (the default) will export all related data

 

Extra Information section

 

Detailed Report instructionStep adds Thread ID and timestamp information to the report

 

Show Source Code instructionStep if choosing a detailed report, includes the source code fragments displayed with each callstack

 

Colour Coded Report instructionStep for HTML reports, exports a coloured HTML table layout

 

The colour scheme is not configurable.

 

If you want a custom style, export a detailed XML report and process that to generate the HTML report.

 

 

File section

 

File options are relevant whether exporting an Objects Report or a Memory Report.

 

File instructionStep type the filename or Browse to a location

 

Format instructionStep set whether exporting HTML or XML

 

Defaults to the menu option selected, but included here to more easily export one format and then the other.

 

Encoding instructionStep set whether UTF-16 LE, UTF-8 or ASCII encoding. By default the exported file is saved in the Windows Unicode format UTF-16 little endian. You can also save in UTF-8 and ASCII. ASCII has no byte order mark at the start of the file.

 

OK instructionStep exports the session data

 

Check the overwrite existing file option if you want to be warned about overwrites.