JDK-8182774 : Verify code in javap
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javap
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-06-23
  • Updated: 2024-08-27
  • Resolved: 2024-05-31
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 23
23 b26Fixed
Related Reports
Blocks :  
CSR :  
Relates :  
Sub Tasks
JDK-8331129 :  
Description
It would be great if javap had a 'plugin' which allowed verification of 
underlying bytecode, which could be ran in isolation. This could be an 
useful tool to diagnose verifier error in the VM and, at the same time, 
to get better output out of the verification process. Most bytecode APIs 
do have some verification tool - ASM one is called CheckClassAdapter:

http://asm.ow2.org/asm40/javadoc/user/org/objectweb/asm/util/CheckClassAdapter.html

while BCEL one is called Verifier:

https://commons.apache.org/proper/commons-bcel/apidocs/org/apache/bcel/verifier/Verifier.html

The verifier could be implemented either on top of javap - or, maybe, on 
top of the new bytecode API, whichever is easier.
Comments
Changeset: a7864af0 Author: Adam Sotona <asotona@openjdk.org> Date: 2024-05-31 08:48:14 +0000 URL: https://git.openjdk.org/jdk/commit/a7864af08acbe63d09f770ca66780738260faac4
31-05-2024

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/18629 Date: 2024-04-04 15:13:46 +0000
02-05-2024

Draft PR: https://github.com/openjdk/jdk/pull/18629
04-04-2024

It would be great if we could leverage the "real" verifier in the JVM ...
23-06-2017