In this release FINALLY blocks now execute as part of STOP processing if using the CatchStop (-catchStop) startup parameter. Prior to this release if you get a STOP condition in a block, the AVM does not run any FINALLY block unless the STOP condition is handled by either a local CATCH block or an ON STOP phrase. Now, with -catchStop 1, STOP conditions behave more like errors. Even if the STOP condition is not handled in the current block, the AVM runs a local FINALLY block. There are still a few, rare conditions that cause STOP to bubble up to the top of a transaction block, or out to a layer that does not access the database, and not abide by any ON STOP or relevant CATCH blocks along the way. For those conditions, FINALLY blocks along that path will not run either.
