CommandProcessor command "dumpclass" produces classes with invalid field descriptors.
`ClhsdbDumpclass` uses javap to verify classes validity.
Javap prints errors related to invalid constant pool entries, however the exit code is 0 and `ClhsdbDumpclass` test pass with invalid entries.
Work onJDK-8294969 "Convert jdk.jdeps javap to use the Classfile API" triggered `ClhsdbDumpclass` test to start failing on invalid entries.
Root cause of the problem is in `sun.jvm.hotspot.oops.InstanceKlass::getFieldSignatureIndex` returning `getGenericSignatureIndex` instead of `getSignatureIndex`.
`ClhsdbDumpclass` uses javap to verify classes validity.
Javap prints errors related to invalid constant pool entries, however the exit code is 0 and `ClhsdbDumpclass` test pass with invalid entries.
Work on
Root cause of the problem is in `sun.jvm.hotspot.oops.InstanceKlass::getFieldSignatureIndex` returning `getGenericSignatureIndex` instead of `getSignatureIndex`.
- relates to
-
JDK-8292818 replace 96-bit representation for field metadata with variable-sized streams
-
- Resolved
-
-
JDK-8316342 CLHSDB "dumpclass" command produces invalid classes
-
- Resolved
-
