Marker Types

Recording markers are similar to breakpoints; however, instead of breaking execution as it does at a breakpoint, the debugger takes the action defined by the type of marker. If the marker is denoted as a recording start point, the debugger immediately begins to trace all executed calls from that point for the breaking thread. Recording is stopped again when either the thread that is being captured terminates or the thread encounters a recording end point.

Recording markers are set in the source code editor. If you right-click on the breakpoint margin at the point to begin recording, a context menu displays that enables you to select the type of a marker.

Use to

Set Start and End points for recording
Set Markers for a Single Method
Set Stack Trace Markers

Reference

Marker

Detail

See also

Start Recording marker

 

End Recording marker

Select the Add Start Recording Marker option, then right-click on the breakpoint margin at the point to stop recording and select the Add End Recording Marker context menu option; the markers are shown below:
 

recordingmarkers2
 

When the debugger is executed it continues to run the thread, recording a stack history until either the End Recording marker is encountered or the thread terminates, unlike normal breakpoints where the debugger halts and displays the line of code.

In order to limit the amount of  information being collected, you can control the stack depth being recorded.

Recording markers can be nested. This will result in the recording stack depth being reset when a new recording marker is hit. Begin and End recording markers still need to be carefully matched.

 

The Breakpoints & Events Window

 

 

 

 

 

Analyzer Script Editor

 

 

 

 

 

 
Control Stack Depth

Stack Auto-Capture marker

 
stackmarkerineditor
 

(Native Code only) Stack markers enable you to capture any unique stack traces that occur at a point in an application; they provide a quick and useful picture of where a point in an application is being called from.

To insert a marker at the required point in code, right-click on the line and select the Add Stack Auto Capture Marker context menu option.

Each time the debugger encounters the marker it performs a stack trace; if the stack trace is not in the recording history, it is copied, and the application continues running.

 

 

Method Auto Record marker

A Method Auto Record marker enables you to record activity for a particular function during a debug session; the debugger records any function calls executed after the marker point, and always stops recording when this function exits.

The function marker combines a Start Recording marker and an End Recording marker in one.
 

Autorecordmarker

 

Recording markers can be nested. When a new Method Auto Record marker is hit while recording the stack depth to record to will be extended to cover the current method and the required depth from that function.

 

 

Learn more

Learning Center topics

(Alt+F1) | Execution Analysis | Recording Execution | Method Record Marker