JDK-8190936 : [lworld] Missing SA support causes "sun.jvm.hotspot.utilities.AssertionFailure: illegal bci"
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc-agent
  • Affected Version: repo-valhalla
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-11-08
  • Updated: 2025-09-10
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.
Other
repo-valhallaUnresolved
Related Reports
Relates :  
JDK-8366705 - [lworld] Re-work of arrays meta-data
Relates :  
JDK-8366806 - [lworld] JDI test failures
Description
Lack of support for new bytecodes, causes sun.jvm.hotspot.utilities.AssertionFailure: illegal bci in:

serviceability/sa/ClhsdbJstack.java 
serviceability/sa/ClhsdbPrintStatics.java
serviceability/sa/ClhsdbSymbol.java
serviceability/sa/ClhsdbWhere.java
serviceability/sa/JhsdbThreadInfoTest.java
serviceability/sa/TestCpoolForInvokeDynamic.java
serviceability/sa/TestHeapDumpForInvokeDynamic.java
serviceability/sa/TestHeapDumpForLargeArray.java
serviceability/sa/TestIntConstant.java
serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java

Will need problem listing until we go from EA to integration

UPDATE: There are now about 25 tests problem listed due to this failure. Hard to say if they are all due to the same issue or if this CR has just become a place to collect SA failures.
Comments
JDK-8366705 has introduced a large number of additional failures. Probably need to address that first because it possibly is also causing the tests already problem listed by this CR to fail.
09-09-2025
This CR was filed in 2017. Hard to say if the originally filed issues still exits.The more recent failure could be something completely different.
02-07-2024
serviceability/sa/ClhsdbDumpclass.java now fails as well with a different failure mode: java.lang.ArrayIndexOutOfBoundsException: -25922 17 at jdk.hotspot.agent/sun.jvm.hotspot.oops.ResolvedFieldArray.getAt(ResolvedFieldArray.java:60) at jdk.hotspot.agent/sun.jvm.hotspot.oops.ConstantPoolCache.getFieldEntryAt(ConstantPoolCache.java:93) at jdk.hotspot.agent/sun.jvm.hotspot.tools.jcore.ByteCodeRewriter.rewrite(ByteCodeRewriter.java:121) at jdk.hotspot.agent/sun.jvm.hotspot.tools.jcore.ClassWriter.rewriteByteCode(ClassWriter.java:759) at jdk.hotspot.agent/sun.jvm.hotspot.tools.jcore.ClassWriter.writeMethod(ClassWriter.java:647) at jdk.hotspot.agent/sun.jvm.hotspot.tools.jcore.ClassWriter.writeMethods(ClassWriter.java:491) at jdk.hotspot.agent/sun.jvm.hotspot.tools.jcore.ClassWriter.write(ClassWriter.java:97) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor$54.doit(CommandProcessor.java:1873) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:2212) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.executeCommand(CommandProcessor.java:2182) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor.run(CommandProcessor.java:2053) at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.run(CLHSDB.java:112) at jdk.hotspot.agent/sun.jvm.hotspot.CLHSDB.main(CLHSDB.java:44) at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runCLHSDB(SALauncher.java:281) at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:500) ] I'll use this bug ID to problem list it.
22-03-2024
open ProblemListed.txt
23-11-2017