Application Exception Occurred dialog box

Restriction: The Application Exception Occurred dialog box is not available when debugging on the AS/400.

The behavior of the Application Exception Occurred dialog box changes depending on the platform running the program you are debugging. The dialog box is available when debugging on the AIX, OS/390, Solaris, or Windows NT platform.

Select the appropriate platform:

ngaix.gif (307 bytes)ngwin.gif (301 bytes) Application Exception Occurred dialog box

The Application Exception Occurred dialog box opens when, during program execution, an exception is encountered that matches one of the exceptions that are specified in the Exception Filter Preferences Settings dialog box. The line where the exception occurred is highlighted in the Source pane.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Push buttons
OK Closes the Application Exception Occurred dialog box. The line where the exception occurred is highlighted in the Source pane when the dialog box is closed.
Help Displays this help.

After a program exception is encountered and the Application Exception Occurred dialog box is closed, the following actions are available:

Step Exception This action is selected by clicking step exception button in the toolbar, selecting Debug > Step Exception from the menu bar, or by pressing F6.

Selecting this action causes the debugger to step into the first registered exception handler (tracked by the operating system). Execution stops at the first executable line of code in the exception handler. If your application does not have a registered condition handler, the condition remains unhandled and the application may be terminated.

ngjava.gif (312 bytes) When debugging interpreted Java programs, exceptions are handled through try/catch/finally mechanism. Selecting Step Exception causes the debugger to step into the first catch clause that handles the exception that was thrown. Execution stops at the first executable line of code in the catch block. If the exception is not caught by your application, the exception remains unhandled and the application may be terminated.

Run Exception This action is selected by clicking run exception button in the toolbar or by selecting Debug > Run Exception from the menu bar.

Selecting this action causes the debugger to run the exception handler that is registered to handle the type of exception encountered.

ngjava.gif (312 bytes) When debugging interpreted Java, selecting this action causes the debugger to run the catch block that handles the type of exception encountered.

Examine/Retry Exception This action is selected by clicking examine/retry exeception button in the toolbar or by selecting Debug > Examine/Retry Exception from the menu bar.

Selecting this action allows you to investigate the cause of the exception and, if desired, retry program execution at the statement that triggered the exception. The debugger begins at this statement and attempts to continue.

Note: When debugging on Solaris, if you select this option in a multithreaded program, the exception will re-occur when the thread terminates, and you will be unable to continue debugging the program.

ng390.gif (283 bytes)Application Exception Occurred dialog box

The Application Exception Occurred dialog box opens when, during program execution, an exception is encountered that meets one of the exception types or the exception level specified. The line where the exception occurred is highlighted in the Source pane.

Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.

Push buttons
OK Closes the Application Exception Occurred dialog box. The line where the exception occurred remains highlighted in the Source pane.
Help Displays this help.

After a program exception is encountered and the Application Exception Occurred dialog box is closed, the following actions are available:

Step Exception This action is selected by clicking step exception button in the toolbar, selecting Debug > Step Exception from the menu bar, or by pressing F6.

Selecting this action causes the debugger to step into the first registered exception handler (tracked by the operating system). Execution stops at the first executable line of code in the exception handler. If your application does not have a registered condition handler, the condition remains unhandled and the Language Environment may terminate the application.

ngjava.gif (312 bytes) When debugging interpreted Java programs, exceptions are handled through try/catch/finally mechanism. Selecting Step Exception causes the debugger to step into the first catch clause that handles the exception that was thrown. Execution stops at the first executable line of code in the catch block. If the exception is not caught by your application, the exception remains unhandled and the Language Environment may terminate the application.

Run Exception This action is selected by clicking run exception button in the toolbar or by selecting Debug > Run Exception from the menu bar.

Selecting this action causes the debugger to run the exception handler that is registered to handle the type of exception encountered.

ngjava.gif (312 bytes) When debugging interpreted Java, selecting this action causes the debugger to run the catch block that handles the type of exception encountered.

Examine/Retry Exception This action is selected by clicking examine/retry exeception button in the toolbar or by selecting Debug > Examine/Retry Exception from the menu bar.

Selecting this action allows you to investigate the cause of the exception. You cannot retry program execution at the statement that triggered the exception. With this selection, the exception is considered to be handled by the debug engine and does not continue to percolate in your code. The Distributed Debugger continues at the statement just after the one that triggered the exception.

Attention: Selecting this action alters the program flow and the state of the program becomes undefined if program execution continues beyond this point. For example, exceptions may no longer be caught even it there is a catch clause for the exception.