Please enable JavaScript to view this site.

Memory Validator Help

The Trace Hooks tab provides controls for:


how TRACE hooks are installed

tracking duplicate or invalid handles

controlling maximum duration of the memory timeline






Trace message monitoring


Memory Validator can optionally collect the output from AfxTrace(), TRACE macros and the OutputDebugString() function.


OutputDebugString() sends a string to the debugger for display:




TRACE messages are macros, for example:


 TRACE( "This is a TRACE statement\n" );


The TRACE macros ultimately get routed via OutputDebugString(), so to prevent duplicate messages, we don't allow both to be collected at the same time.


Collect trace messages instructionStep enables collection of either OutputDebugString() or TRACE messages


OutputDebugString instructionStep collect OutputDebugString() messages


To collect the relevant callstacks, select Collect OutputDebugString() call stack


Trace (TRACE(), AfxTrace()...) instructionStep collect TRACE messages


To collect the callstacks, select the Collect TRACE call stack



Example of trace statements collected in the Analysis tab:





Reset All - Resets all global settings, not just those on the current page.



Reset - Resets the settings on the current page.