Version 6.3.13 for Windows
 —  Debugger  —

Using the Call Stack

This document covers the following topics:


About the Call Stack

The call stack window lists the objects which have been called during the current debugging session in hierarchical order.

The latest object is always shown at the top of the list. The variables window shows all variables which belong to this object by default. For example, when you step into a subprogram, this subprogram is shown at the top of the list and the variables window automatically shows the variables for this subprogram.

You can bring the editor window for a specific object to the front by double-clicking the corresponding entry in the call stack window.

Notes:

  1. A gray arrow in the editor window indicates the position at which the previous object in the call stack hierarchy was invoked.
  2. If copycode is debugged, the call stack does not contain an additional entry for this copycode.

Top of page

Displaying the Source Code of a Different Object

For each object listed in the call stack, you can display the source code and thus bring its editor window to the front. There are different commands for this purpose:

Start of instruction setTo go to the source code of a different object

Start of instruction setTo go to the source code of a different object and display the variables of this object

Top of page

Returning to the Object at the Current Trace Position

When you have displayed the source code of a different object, you can return to the object at the current trace position (which is indicated by an arrow) and thus bring its editor window to the front.

Start of instruction setTo return to the object at the current trace position

Top of page