Debugging the Method Call Stack
The Debug button displays a Call Stack Browser. The Call Stack Browser enables you to browse methods in the call stack, and inspect parameters and local variables.
The Call Stack Browser is also displayed when you call the
The exception, including the method call stack history and the exception stack history, is also written to the log file of the current application (for example, MyApp.log). The exception stack history section contains at least the error code of each of the nested exceptions.
The following image shows an example of the Call Stack Browser, with the EconAgent class ad1 property
Use the Inspect Item command from the Inspect menu to display the value of a primitive item or to inspect an item containing an object reference.
To copy the current call stack to the clipboard as a string
-
Right‑click on the call stack results.
-
Select the Copy Call Stack to Clipboard command from the popup menu that is then displayed.
Call stack entries copied to the clipboard are delimited by carriage return / line feed characters (CrLf).
To inspect the value of the item on which the caret is positioned
-
Perform one of the following actions.
-
Select the Inspect Item command from the Inspect menu
-
Press Ctrl+I
-
If the item being inspected contains a primitive type, an invalid object reference, or a null object reference, a dialog is then displayed. (An example of this dialog is shown in the previous image.)
If the item contains an object reference, an Inspector form for the object is then displayed. The selected object, and any properties defined for that object, is displayed in the left of the Inspector form.
To view the values in the Inspector form for the displayed properties
-
Click on the required property.
The values for the property are then displayed in the pane at the right of the form.
For more details, see Chapter 7 of the JADE Development Environment User’s Guide, "
To exit from the Call Stack Browser
-
Select the Exit command from the File menu.
The Call Stack Browser is then closed, and focus returns to the Unhandled Exception dialog.
