The fix for BYTEMAN-172 reesolved the verify error thrown by JDK7 by generating 3 separate exception throws for a rethrow handler planted inside a synchronized region, one for each of the Byteman exception types, even though they are all essentially the same. It would be more efficient if a single handler was generated for the parent type ExecuteException.

n.b. Implementation of this enhancement requires knowing at the point of exit from a trigger injection region whether the trigger is located within a synchronized region. The current algorithm only makes this information available at the end of the basic block containing the injected trigger code rather than at the end of the trigger region.