IV72386: RUNNING INVOKEDYNAMIC BYTECODES IN DEBUG (JVMTI) SCENARIOS CAN O CCASIONALLY CAUSE A CRASH

APAR status

• Closed as program error.

Error description

• Error Message: Typically:Unhandled exceptionType=Segmentation
  error vmState=0x00000000
  .
  Stack Trace:
  .
  This will typically be seen when running a test case involving
  invokedynamic (for example, lambdas) in a debugger like Eclipse.
  

Local fix

Problem summary

• The jit compiler was incorrectly generating a "resolve check" in
  the incorrect location for an invokedynamic bytecode. The
  resulting generated code would attempt to access an
  invokedynamic's CallSite or MethodType information before it was
  resolved, resulting in a crash. This would occur only if the
  invokedynamic bytecode was never executed by the interpreter
  before being jit compiled, which is unusual.
  

Problem conclusion

• The jit compiler was fixed to generate the "resolve check" in
  the correct location.
  .
  This APAR will be fixed in the following Java Releases:
   7 R1 SR3 (7.1.3.0)
   7 SR9 (7.0.9.0)
   8 SR1 (8.0.1.0)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  Service Refreshes and Fix Packs can be found at:
   https://www.ibm.com/developerworks/java/jdk/
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

• Fixed component name

  JIT

• Fixed component ID

  620700124

Applicable component levels

• R130 PSY

     UP

• R260 PSY

     UP