Community
Participate
Working Groups
Due to multi catch being implemented as a single code block with multiple possible unrelated exception types flowing through it, we need to guard on calls to handler related advice to check the exception is what was specified at match time. See test testMultiCatchWithHandler2 in Ajc170Tests (need to run it to see verifyerror)
likely needs a change in BcelClassWeaver.match(LazyMethodGen,InstructionHandle,BcelShadow,List<BcelShadow>) to recognize multi catch, and tell the created exception handler shadows that they need a test in any residue.