Process First Chance Exceptions

Access    Debug & Record Toolbar: DebugOpt | Process First Chance Exceptions




See also

Debug Process

When an application is being debugged and the debugger is notified of an exception, the application is paused and the debugger responds in the way it is configured to do; it either:

Resumes the application and leaves the exception to the application to manage, or
Keeps the application suspended and passes the exception to the appropriate routines for automatic resolution or manual intervention



Second Chance Exceptions

The Enterprise Architect debugger defaults to the first behavior, above.

If the application can handle the exception, it continues to process; if it cannot handle the exception, the debugger is notified again and this time it must suspend the application and resolve the exception condition.

In this behavior, because the debugger has encountered the exception twice, it is known as a second-chance exception; in this case, if the exception does not halt execution, it is ignored and you avoid spending time on conditions that do not impact the overall outcome of processing.

You might work this way on large or complex systems that invariably involve exception conditions somewhere in the processing paths.



First Chance Exceptions

However, if you want to examine every exception that occurs as soon as it occurs, you can set the debugger to adopt the second behavior.

Because the debugger responds to the exception on first contact, it is known as a first-chance exception.

You might work this way with individual functions or routines that must work cleanly or not at all.




Select the Process First Chance Exceptions option to debug exceptions on first contact.

Deselect the option to process exceptions only if the application fails when they occur.