View the Call Stack

The Call Stack window is used to display all currently running threads in a process. It can be used to identify which thread is operational immediately before program failure occurs.

When a Simulation is active, the Call Stack will show the current execution context for the running simulation. This will include a separate context stack for each concurrent simulation "thread".

A stack trace is displayed whenever a thread is suspended, through one of the step actions or through encountering a breakpoint. The Call Stack window can record a history of stack changes, and enables you to generate Sequence diagrams from this history.

Access Analyzer | Call Stack

Use to

•

View stack history to understand the execution of a process

•

View threads

•

Save a call stack for later use

•

Record call stack changes for Sequence diagram generation

•

Generate a Sequence diagram from the call stack

•

View the related code line in the Source Code Editor

Topics

Topic

Detail

See also

Indicators

•

A pink arrow highlights the current stack frame

•

A blue arrow indicates a thread that is running

•

A red arrow indicates a thread for which a stack trace history is being recorded

Save a Call Stack to a .TXT File

Not currently available.

Record a Thread in a Debug Session

To record the execution of a thread and direct the recording to the Record & Analyze window, right-click on the thread in the call stack and select the appropriate context menu option:

•

Record - to manually record the current thread during the debug sessionUsed in conjunction with the 'step' buttons of the debugger; each function that is called due to a step command is logged to the Record & Analyze window.

•

Auto-Record - to perform auto-recording during a debug sessionWhen you select this icon, the Analyzer begins recording and does not stop until either the program ends, you stop the debugger or you click on the Stop icon.