JDK-8075730 : Old bytecode verifier accepts illegal class
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2015-03-23
  • Updated: 2016-12-19
  • Resolved: 2016-05-09
Related Reports
Relates :  
JDK-7127066 - Class verifier accepts an invalid class file
Sub Tasks
JDK-8075766 :  
4.10.2.2: Clarify details for exceptional local variable array - Closed
Description
The bytecode (old) verifier accepts the attached classes even though the number of locals are not always sufficient for the protecting exception handler.  Instead, a VerifyError exception should be thrown.  The attached files are test cases and contain details about the bytecodes where there are insufficient locals.
Comments
The stackmaps for these test cases have been manipulated to create an illegal class. The split verifier will detect this but the old verifier will not because the old verifier ignores stackmaps. We don't plan to change the old verifier to understand stackmaps.
09-05-2016
This is the same issue as JDK-7127066 except that bug concerned the split verifier and this one concerns the bytecode verifier.
23-03-2015