The following test failed with SIGSEGV in the Valhalla CI:

vmTestbase/nsk/jdb/use/use001/use001.java

Here's a snippet from the log file:

[8:28:13.504] reply[0]: main[1]
[8:28:13.504] Sending command: use
[8:28:13.705] reply[0]: /opt/mach5/mesos/work_dir/jib-master/install/jdk-27-valhalla+1-70/src.full/open/test/hotspot/jtreg/vmTestbase/nsk/jdb/use/use001:/opt/mach5/mesos/work_dir/slaves/da1065b5-7b94-4f0d-85e9-a3a252b9a32e-S86860/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/eee9bd6b-6060-4e21-8670-bf41e962c16c/runs/98c706d6-a137-4a15-a50b-c7e3495b0f93/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdb/classes/0/vmTestbase/nsk/jdb/use/use001/use001.d:/opt/mach5/mesos/work_dir/slaves/da1065b5-7b94-4f0d-85e9-a3a252b9a32e-S86860/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/eee9bd6b-6060-4e21-8670-bf41e962c16c/runs/98c706d6-a137-4a15-a50b-c7e3495b0f93/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdb/classes/0/vmTestbase/nsk/jdb/use/use001/use001.d/vmTestbase:/opt/mach5/mesos/work_dir/slaves/da1065b5-7b94-4f0d-85e9-a3a252b9a32e-S86860/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/eee9bd6b-6060-4e21-8670-bf41e962c16c/runs/98c706d6-a137-4a15-a50b-c7e3495b0f93/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdb/classes/0/vmTestbase/nsk/jdb/use/use001/use001.d/test/lib
[8:28:13.705] reply[1]: main[1]
[8:28:13.712] Sending command: cont
[8:28:20.922] reply[0]: > #
[8:28:20.922] reply[1]: # A fatal error has been detected by the Java Runtime Environment:
[8:28:20.922] reply[2]: #
[8:28:20.922] reply[3]: # SIGSEGV (0xb) at pc=0x0000ffff14acab90, pid=3511864, tid=3511884
[8:28:20.922] reply[4]: #
[8:28:20.922] reply[5]: # JRE version: Java(TM) SE Runtime Environment (27.0+1) (fastdebug build 27-valhalla+1-70)
[8:28:20.922] reply[6]: # Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 27-valhalla+1-70, compiled mode, sharing, compressed class ptrs, g1 gc, linux-aarch64)
[8:28:20.922] reply[7]: # Problematic frame:
[8:28:20.922] reply[8]: # C 0x0000ffff14acab90
[8:28:20.922] reply[9]: #
[8:28:20.922] reply[10]: # Core dump will be written. Default location: Determined by the following: "/opt/core.sh %p" (alternatively, falling back to /opt/mach5/mesos/work_dir/slaves/da1065b5-7b94-4f0d-85e9-a3a252b9a32e-S86860/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/eee9bd6b-6060-4e21-8670-bf41e962c16c/runs/98c706d6-a137-4a15-a50b-c7e3495b0f93/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdb/scratch/2/core.3511864)
[8:28:20.922] reply[11]: #
[8:28:20.922] reply[12]: # An error report file with more information is saved as:
[8:28:20.922] reply[13]: # /opt/mach5/mesos/work_dir/slaves/da1065b5-7b94-4f0d-85e9-a3a252b9a32e-S86860/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/eee9bd6b-6060-4e21-8670-bf41e962c16c/runs/98c706d6-a137-4a15-a50b-c7e3495b0f93/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdb/scratch/2/hs_err_pid3511864.log
[8:28:20.922] reply[14]: #
[8:28:20.922] reply[15]: # Compiler replay data is saved as:
[8:28:20.922] reply[16]: # /opt/mach5/mesos/work_dir/slaves/da1065b5-7b94-4f0d-85e9-a3a252b9a32e-S86860/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/eee9bd6b-6060-4e21-8670-bf41e962c16c/runs/98c706d6-a137-4a15-a50b-c7e3495b0f93/testoutput/test-support/jtreg_open_test_hotspot_jtreg_vmTestbase_nsk_jdb/scratch/2/replay_pid3511864.log
[8:28:20.922] reply[17]: #
[8:28:20.922] reply[18]: # If you would like to submit a bug report, please visit:
[8:28:20.922] reply[19]: # https://bugreport.java.com/bugreport/crash.jsp
[8:28:20.922] reply[20]: #
[8:28:20.922] reply[21]:
[8:28:20.922] reply[22]: The application has been disconnected
[8:28:20.922] Sending command: quit
[8:28:20.932] # ERROR: Caught unexpected exception while executing the test: nsk.share.Failure: Debuggee did not exit after 1 <cont> commands
The following stacktrace is for failure analysis.
nsk.share.TestFailure: Caught unexpected exception while executing the test: nsk.share.Failure: Debuggee did not exit after 1 <cont> commands
at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:309)
at nsk.share.Log.complain(Log.java:280)
at nsk.share.jdb.JdbTest.failure(JdbTest.java:72)
at nsk.share.jdb.JdbTest.runTest(JdbTest.java:157)
at nsk.jdb.use.use001.use001.main(use001.java:73)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
nsk.share.Failure: Debuggee did not exit after 1 <cont> commands
at nsk.share.jdb.Jdb.contToExit(Jdb.java:890)
at nsk.jdb.use.use001.use001.runCases(use001.java:134)
at nsk.share.jdb.JdbTest.runTest(JdbTest.java:148)
at nsk.jdb.use.use001.use001.main(use001.java:73)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:335)
at java.base/java.lang.Thread.run(Thread.java:1516)
[8:28:20.945] Waiting for jdb exits
[8:28:21.77] jdb normally exited
[8:28:21.78] # ERROR: TEST FAILED

Here's the crashing thread's stack from the hs_err_pid file:

--------------- T H R E A D ---------------

Current thread (0x0000ffff9c1dcde0): JavaThread "C2 CompilerThread0" daemon [_thread_in_vm, id=3511884, stack(0x0000ffff41caf000,0x0000ffff41ead000) (2040K)]


Current CompileTask:
C2:20544 1928 b jdk.internal.classfile.impl.Util::entryList (53 bytes)

Stack: [0x0000ffff41caf000,0x0000ffff41ead000], sp=0x0000ffff41ea8b00, free space=2022k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C 0x0000ffff14acab90
C 0x0000000000000907

siginfo: si_signo: 11 (SIGSEGV), si_code: 2 (SEGV_ACCERR), si_addr: 0x0000ffff14acab90

This is a jdb test crashing in C-code so I would normally start this issue
in hotspot/jvmti, but it's the "C2 CompilerThread0" that crashed so I'm
starting this issue in hotspot/compiler for initial triage.