Don't override error codes from bytecode verification #22849
      
        
          +4
        
        
          −3
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
#13444 changes the order of verification for exceptions and bytecodes. This resulted in the error message "thrown object not throwable" for exception verification to be set for bytecode verification failures. This change does not override error codes for bytecode verification which was being done previously.
This was pointed out in #22812.
With this change
java.lang.VerifyError: JVMVRFY021 thrown object not throwable; class=com/acme/FailVerify, method=explode(Ljava/lang/String;)V, pc=4becomes:
Exception in thread "main" java.lang.VerifyError: JVMVRFY012 stack shape inconsistent; class=com/acme/FailVerify, method=explode(Ljava/lang/String;)V, pc=4