Call stack tool: Interface

The call stack tool provides information, at a particular point during system execution, about the call stack of a system being executed under control of the debugger.

The call stack is composed of a list representing the call stack elements, in which the root procedure of the system is at the bottom of the list and the currently executing routine is at the top.

  • The currently selected call stack element, to which the other debugger tools refer, is indicated by a green arrow .
  • Clicking on a call stack element represented by an empty arrow , or picking the element and dropping it onto either the call stack list or the locals view defines it as being the currently selected call stack element.
  • The call stack elements with no icon are called external call stack elements, they represent a call stack out of Eiffel, for example, a true .NET call stack.
  • For each feature in the call stack, the name, dynamic class, and static class are displayed. The dynamic class is the type of the object upon which the feature is called, whereas the static class is the class in which the feature was written.
  • An asterisk next to the name of a feature means the feature is melted, as opposed to frozen.

At the top of the list, one line of text gives the state of the debugged application, in this case "Status = Breakpoint reached". A second line describes the exception that caused the application to stop, if any. In the case shown above, execution stopped at a breakpoint, so no exception is shown on the second line. For more information concerning exceptions, see the supported exceptions. The button is used to open the Exception dialog which show the exception details. For instance a call on Void target in a .NET system would popup :

When more than one thread is available to the debugger, you can switch from one thread to another. To do that, click on the thread's id "0x000..." and select from the pop-up list of available threads. Or (recommended) you can use the threads tool (clicking on Show threads panel will show the threads tool).

In the toolbar, the button gives you the capability to save the call stack to a text file. The button can be used to copy the call stack to the clipboard. The button makes it possible to choose a desired depth for the call stack in the list (the default is to display the 100 top stack elements).

ff70f68f-31db-c5d1-4d68-7b0fc70b1dd7