In VisualAge Smalltalk and VA Smalltalk 8.0 and earlier, if an exception occurred while execution an Exception’s defaultAction or an ExceptionalEvent’s defaultAction, there were no exception handlers available to handle the exception since the chain of exception handlers had been followed to the end before executing the defaultAction.

Additionally, if another exception occurred in a protected block after an exception handler had been executed, that exception might not have been handled properly since some or all of the chain of exception handlers had been consumed.

The exception handling code has been updated to restore the chain of exception handlers before executing the defaultAction for an exception and before resuming or exiting from an exception handler.

Since the exception handling behavior has changed in situations where multiple exceptions occur in a protected block (or nested protected blocks), you should evaluation your exception handling strategy to ensure this change does not adversely affect your application.