Even with the fix for JDK-8022066 MethodHandleConstants.java still fails.

Note: there were significant changes to the 292 implementation recently and an updated version of JDK-8022066 was merged into the jdk8 mainline. The experts in this area have been notified, and are aware of this issue. The test has been added to the ProblemList.txt, and should be removed when this bug is fixed.

Sample failure.

TEST: java/lang/invoke/MethodHandleConstants.java
JDK under test: (/opt/jprt/T/P1/131320.chhegar/testproduct/linux_i586_2.6-product)
java version "1.8.0-internal"
Java(TM) SE Runtime Environment (build 1.8.0-internal-201310141313.chhegar.tl_13_04_staging-b00)
Java HotSpot(TM) Client VM (build 25.0-b53, mixed mode, sharing)


ACTION: build -- Passed. All files up to date
REASON: User specified action: run build indify.Indify
TIME: 0.0 seconds
messages:
command: build indify.Indify
reason: User specified action: run build indify.Indify
elapsed time (seconds): 0.0

ACTION: compile -- Passed. Compilation successful
REASON: User specified action: run compile MethodHandleConstants.java
TIME: 0.028 seconds
messages:
command: compile /opt/jprt/T/P1/131320.chhegar/s/jdk/test/java/lang/invoke/MethodHandleConstants.java
reason: User specified action: run compile MethodHandleConstants.java
elapsed time (seconds): 0.028

ACTION: build -- Passed. All files up to date
REASON: Named class compiled on demand
TIME: 0.0 seconds
messages:
command: build indify.Indify
reason: Named class compiled on demand
elapsed time (seconds): 0.0

ACTION: main -- Failed. Unexpected exit from test [exit code: 134]
REASON: User specified action: run main/othervm indify.Indify --verify-specifier-count=0 --expand-properties --classpath ${test.classes} --java test.java.lang.invoke.MethodHandleConstants --check-output
TIME: 0.202 seconds
messages:
command: main indify.Indify --verify-specifier-count=0 --expand-properties --classpath ${test.classes} --java test.java.lang.invoke.MethodHandleConstants --check-output
reason: User specified action: run main/othervm indify.Indify --verify-specifier-count=0 --expand-properties --classpath ${test.classes} --java test.java.lang.invoke.MethodHandleConstants --check-output
elapsed time (seconds): 0.202
STDOUT:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x405289fa, pid=1589, tid=1670151056
#
# JRE version: Java(TM) SE Runtime Environment (8.0) (build 1.8.0-internal-201310141313.chhegar.tl_13_04_staging-b00)
# Java VM: Java HotSpot(TM) Client VM (25.0-b53 mixed mode, sharing linux-x86 )
# Problematic frame:
# V [libjvm.so+0x4fc9fa] SystemDictionary::find_method_handle_invoker(Symbol*, Symbol*, KlassHandle, Handle*, Handle*, Thread*)+0x4aa
#
# Core dump written. Default location: /opt/jprt/T/P1/131320.chhegar/s/jdk/build/linux-i586/testoutput/jdk_lang/JTwork/scratch/core or core.1589
#
# An error report file with more information is saved as:
# /opt/jprt/T/P1/131320.chhegar/s/jdk/build/linux-i586/testoutput/jdk_lang/JTwork/scratch/hs_err_pid1589.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#
STDERR:
patching test/java/lang/invoke/MethodHandleConstants.main(L)V
46:invokestatic 10 MH_String_replace_C2()L => ldc 299:MethodHandle[5, 298]
79:invokestatic 16 MH_MethodHandle_invokeExact_SC2()L => ldc 302:MethodHandle[5, 301]
117:invokestatic 19 MH_MethodHandle_invoke_SC2()L => ldc 305:MethodHandle[5, 304]
155:invokestatic 21 MH_Class_forName_S()L => ldc 308:MethodHandle[6, 307]
176:invokestatic 23 MH_Class_forName_SbCL()L => ldc 311:MethodHandle[6, 310]

TEST RESULT: Failed. Unexpected exit from test [exit code: 134]