From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: libffi-discuss@sourceware.org
Cc: Andreas Schwab <schwab@linux-m68k.org>,
James Clarke <jrtc27@debian.org>,
Matthias Klose <doko@debian.org>,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>
Subject: [BUG]: libffi 3.3 breaks OpenJDK Zero on 32-bit PowerPC
Date: Fri, 14 Feb 2020 11:14:00 -0000 [thread overview]
Message-ID: <9b5d9318-5ef1-593d-daab-3428818707b5@physik.fu-berlin.de> (raw)
Hello!
After libffi was upgraded to 3.3 in Debian, all OpenJDK versions started
to break on 32-bit PowerPC with the freshly compiled JVM crashing with
the following backtrace:
Thread 2 "java" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf767f450 (LWP 4139976)]
MemoryAccess<int>::get_volatile (this=<optimized out>) at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/share/prims/unsafe.cpp:244
244 T ret = HeapAccess<MO_SEQ_CST>::load_at(_obj, _offset);
(gdb) bt
#0 MemoryAccess<int>::get_volatile (this=<optimized out>) at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/share/prims/unsafe.cpp:244
#1 Unsafe_GetIntVolatile (env=<optimized out>, unsafe=<optimized out>, obj=0xf767e5b4, offset=<optimized out>) at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/share/prims/unsafe.cpp:334
#2 0xf77768e4 in ?? () from /usr/lib/powerpc-linux-gnu/libffi.so.7
#3 0xf7775874 in ?? () from /usr/lib/powerpc-linux-gnu/libffi.so.7
#4 0xf7932690 in CppInterpreter::native_entry (method=<optimized out>, UNUSED=<optimized out>, __the_thread__=0xf7314250)
at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/cpu/zero/interpreterRT_zero.hpp:41
#5 0xf79301cc in ZeroEntry::invoke (__the_thread__=0xf7314250, method=<optimized out>, this=<optimized out>) at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/cpu/zero/entry_zero.hpp:59
#6 CppInterpreter::invoke_method (method=<optimized out>, entry_point=<optimized out>, __the_thread__=__the_thread__@entry=0xf7314250)
at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/share/interpreter/cppInterpreter.cpp:66
#7 0xf7931174 in CppInterpreter::main_loop (recurse=recurse@entry=0, __the_thread__=__the_thread__@entry=0xf7314250)
at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/cpu/zero/bytecodeInterpreter_zero.hpp:87
#8 0xf793187c in CppInterpreter::normal_entry (method=0xf4d96838, UNUSED=<optimized out>, __the_thread__=0xf7314250)
at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/cpu/zero/cppInterpreter_zero.cpp:77
#9 0xf79301cc in ZeroEntry::invoke (__the_thread__=0xf7314250, method=<optimized out>, this=<optimized out>) at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/cpu/zero/entry_zero.hpp:59
#10 CppInterpreter::invoke_method (method=<optimized out>, entry_point=<optimized out>, __the_thread__=__the_thread__@entry=0xf7314250)
at /home/glaubitz/tmp/openjdk/jdk/src/hotspot/share/interpreter/cppInterpreter.cpp:66
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next reply other threads:[~2020-02-14 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 11:14 John Paul Adrian Glaubitz [this message]
2020-02-14 11:46 ` Anthony Green
2020-02-14 11:52 ` John Paul Adrian Glaubitz
2020-02-15 19:03 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b5d9318-5ef1-593d-daab-3428818707b5@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-powerpc@lists.debian.org \
--cc=doko@debian.org \
--cc=jrtc27@debian.org \
--cc=libffi-discuss@sourceware.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).