Displaying and Working With the Call Stack
The Call Stack window contains information about the current call stack at the current position in the methods hierarchy when a run has been suspended. By default, this window is located at the bottom, in a tab adjacent to the Debug Log window. It contains a table of method names corresponding to the thread stack trace. The call stack includes methods, utility classes, and external Java libraries (imported JAR files). Each line contains information about the method name and line number in the Method and Line columns. The name in the Method column follow these rules:
•
For methods corresponding to features in the model (that is, global methods, local methods, and form local methods), the displayed name is the same as in the Method Editor window’s title. For example, method1, form1:method2, and form1:button2:onClick.
•
For methods in utility classes and JAR files, the displayed name is ClassName.methodName.
•
Nested classes are separated with a dot. For example, ClassA.ClassB.ClassC.methodName.
The line number is displayed in the Line column but is not included for imported JAR files.
When you select a row in the table, the corresponding source code is displayed in a Method Editor window (which opens automatically if needed), and the corresponding line is made visible. The line is highlighted in the Method Editor window.
The local variables view is updated to display local variables corresponding to the selected row.
Click the Copy Call Stack to Clipboard button () to copy the content of the current call stack to the clipboard.
When a method is running and not suspended, the Call Stack window retains the most recent values. When the outermost method, command sequence, or event handler finishes its run, the content of the window is cleared.