Salesforce

Runtime Call Stack (Magic xpa 4.x)

« Go Back

Information

 
Created BySalesforce Service User
Approval Process StatusPublished
Objective
Description

Runtime Call Stack (Magic xpa 4.x)

The Runtime Call Stack repository displays the state of the programs that are in the current runtime task tree and the handler that called the new program.

You access this repository by selecting Call Stack from the View menu. The Call Stack option is available when the execution breaks (either by setting a breakpoint or by selecting Debug > Break Now during execution).

The tasks are displayed in the order in which they were executed. The Main Program of the host application will be the first in the list and the current task will be the last in the list.

The Runtime Call Stack repository includes the following columns:

Column

Description

Indicator column

An indicator showing the current line.

Module

The component name (if the executed program is part of a component).

Task

The name of the task that is executed.

Handler

The handler (logic unit) name within the task.

Line

The line number of the operation that is currently executed.

If you double-click on any of these lines, you will go to the Magic xpa task listed there.

The following tool button is available:

  • Display task only – Click this button to display only the name of the program and last task or full path.
    If in the display, there is only one program or a single subtask, it will have no effect.
    If there is more than one level, then the location will be displayed in the following manner:
    <Program name>…<nth task name>

The following context menu option is available:

  • Go to Source – Select this option to go to the source code for the entry currently parked on. The source of the call (the operation that invoked this call) will be displayed. If the task is in a component and the component source is part of the project, the focus will pass to that component.

Note: Component details are only available for programs that are Public.

Multiple Program Entries

A task may appear more than once in the runtime call stack. This may happen when program A calls program B and program B in turn raises an event which is handled in a parent task, that is Program A.

Reference
Attachment 
Attachment