RFR: 8361536: [s390x] Saving return_pc at wrong offset
Amit Kumar
amitkumar at openjdk.org
Thu Jul 10 03:17:18 UTC 2025
On Wed, 9 Jul 2025 05:24:38 GMT, Amit Kumar <amitkumar at openjdk.org> wrote:
> Fixes the bug where return pc was stored at a wrong offset, which causes issue with java abi.
>
> Issue appeared in #26004, see the comment: https://github.com/openjdk/jdk/pull/26004#issuecomment-3017928879.
Fast debug build was fine, but release build crashed with this error:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x000003fffd16b19e, pid=281849, tid=281855
#
# JRE version: OpenJDK Runtime Environment (26.0) (build 26-internal-adhoc.amit.jdk)
# Java VM: OpenJDK 64-Bit Server VM (26-internal-adhoc.amit.jdk, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-s390x)
# Problematic frame:
# V [libjvm.so+0x66b19e] HandleMark::~HandleMark()+0x1e
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -F%F -- %E" (or dumping to /home/amit/jdk/core.281849)
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
stack trace:
Stack: [0x000003fffc900000,0x000003fffca00000], sp=0x000003fffc9fca40, free space=1010k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x66b19e] HandleMark::~HandleMark()+0x1e (handles.inline.hpp:88)
V [libjvm.so+0xc1a038] Threads::create_vm(JavaVMInitArgs*, bool*)+0x528 (threads.cpp:905)
V [libjvm.so+0x799e9a] JNI_CreateJavaVM+0x7a (jni.cpp:3589)
C [libjli.so+0x40e0] JavaMain+0xa0 (java.c:1506)
C [libjli.so+0x8170] ThreadJavaMain+0x20 (java_md.c:646)
This commit (https://github.com/openjdk/jdk/pull/26209/commits/e945e0460832cf25dbbaba351b89c1cade4fefa1) seems to be faulty.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/26209#issuecomment-3052219868
More information about the hotspot-compiler-dev
mailing list