java.lang.RuntimeException: hs-err file incomplete (found 3 matching pattern, first missing pattern: # .*VMError::controlled_crash.*)
at HsErrFileUtils.checkHsErrFileContent(HsErrFileUtils.java:93)
at TestSigInfoInHsErrFile.testWithFPE(TestSigInfoInHsErrFile.java:95)
at TestSigInfoInHsErrFile.main(TestSigInfoInHsErrFile.java:63)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
at java.base/java.lang.Thread.run(Thread.java:1591)
#
# A fatal error has been detected by the Java Runtime Environment:
^^^ Match 0: matches # A fatal error has been detected.*^^^
#
# SIGFPE (0x8) at pc=0x0000fffcf3e2f17c (sent by kill), pid=3120987, tid=3120991
^^^ Match 1: matches # *SIGFPE.*^^^
#
# JRE version: Java(TM) SE Runtime Environment (20.0+24) (fastdebug build 20-ea+24-1803)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 20-ea+24-1803, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
# Problematic frame:
^^^ Match 2: matches # *Problematic frame.*^^^
# C [libpthread.so.0+0xf17c] pthread_kill+0x44
#
# CreateCoredumpOnCrash turned off, no core file dumped
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
--------------- S U M M A R Y ------------
Command Line: -XX:+UnlockDiagnosticVMOptions -Xmx100M -XX:-CreateCoredumpOnCrash -XX:ErrorHandlerTest=15
Host: AArch64, 8 cores, 30G, Oracle Linux Server release 8.6
Time: Thu Nov 17 07:35:47 2022 UTC elapsed time: 0.089260 seconds (0d 0h 0m 0s)
--------------- T H R E A D ---------------
Current thread (0x0000fffcec02b7e0): JavaThread "main" [_thread_in_vm, id=3120991, stack(0x0000fffcf1870000,0x0000fffcf1a70000)]
Stack: [0x0000fffcf1870000,0x0000fffcf1a70000], sp=0x0000fffcf1a6e790, free space=2041k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libpthread.so.0+0xf17c] pthread_kill+0x44
V [libjvm.so+0x18c93f0] VMError::controlled_crash(int)+0x210 (vmError.cpp:1923)
V [libjvm.so+0xfdead8] JNI_CreateJavaVM+0x4d8 (jni.cpp:3662)
C [libjli.so+0x3c50] JavaMain+0x7c (java.c:1457)
C [libjli.so+0x756c] ThreadJavaMain+0xc (java_md.c:650)
C [libpthread.so.0+0x7908] start_thread+0x188
The test expects to see VMError::controlled_crash on a line that starts with # in the hs_err file "header", but that line is pthread_kill. We only see controlled_crash in the stack dump and that doesn't start with #.
at HsErrFileUtils.checkHsErrFileContent(HsErrFileUtils.java:93)
at TestSigInfoInHsErrFile.testWithFPE(TestSigInfoInHsErrFile.java:95)
at TestSigInfoInHsErrFile.main(TestSigInfoInHsErrFile.java:63)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
at java.base/java.lang.Thread.run(Thread.java:1591)
#
# A fatal error has been detected by the Java Runtime Environment:
^^^ Match 0: matches # A fatal error has been detected.*^^^
#
# SIGFPE (0x8) at pc=0x0000fffcf3e2f17c (sent by kill), pid=3120987, tid=3120991
^^^ Match 1: matches # *SIGFPE.*^^^
#
# JRE version: Java(TM) SE Runtime Environment (20.0+24) (fastdebug build 20-ea+24-1803)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 20-ea+24-1803, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
# Problematic frame:
^^^ Match 2: matches # *Problematic frame.*^^^
# C [libpthread.so.0+0xf17c] pthread_kill+0x44
#
# CreateCoredumpOnCrash turned off, no core file dumped
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
--------------- S U M M A R Y ------------
Command Line: -XX:+UnlockDiagnosticVMOptions -Xmx100M -XX:-CreateCoredumpOnCrash -XX:ErrorHandlerTest=15
Host: AArch64, 8 cores, 30G, Oracle Linux Server release 8.6
Time: Thu Nov 17 07:35:47 2022 UTC elapsed time: 0.089260 seconds (0d 0h 0m 0s)
--------------- T H R E A D ---------------
Current thread (0x0000fffcec02b7e0): JavaThread "main" [_thread_in_vm, id=3120991, stack(0x0000fffcf1870000,0x0000fffcf1a70000)]
Stack: [0x0000fffcf1870000,0x0000fffcf1a70000], sp=0x0000fffcf1a6e790, free space=2041k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libpthread.so.0+0xf17c] pthread_kill+0x44
V [libjvm.so+0x18c93f0] VMError::controlled_crash(int)+0x210 (vmError.cpp:1923)
V [libjvm.so+0xfdead8] JNI_CreateJavaVM+0x4d8 (jni.cpp:3662)
C [libjli.so+0x3c50] JavaMain+0x7c (java.c:1457)
C [libjli.so+0x756c] ThreadJavaMain+0xc (java_md.c:650)
C [libpthread.so.0+0x7908] start_thread+0x188
The test expects to see VMError::controlled_crash on a line that starts with # in the hs_err file "header", but that line is pthread_kill. We only see controlled_crash in the stack dump and that doesn't start with #.
- relates to
-
JDK-8296906 VMError::controlled_crash crashes with wrong code and address
-
- Resolved
-