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:

 

 OutputDebugString(msgbuf);

 

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 enables collection of either OutputDebugString() or TRACE messages

 

OutputDebugString collect OutputDebugString() messages

 

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

 

Trace (TRACE(), AfxTrace()...) 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.