[aarch64-port-dev ] Simple HTTP server app crashes on JDK 11 and 8 on OSv AArch64

[Waldek Kozaczuk]

On Mon, Feb 28, 2022 at 8:39 AM Zhengyu Gu <zgu at redhat.com> wrote:

>
>
> On 2/26/22 20:04, Waldek Kozaczuk wrote:
> > OSv v0.55.0-266-g5aedb749
> > eth0: 192.168.122.15
> > Booted up in 92.21 ms
> > Cmdline: java.so -cp /java-example Hello
> > java.so: Starting JVM app using: io/osv/nonisolated/RunNonIsolatedJvmApp
> > java.so: Setting Java system classloader to
> NonIsolatingOsvSystemClassLoader
> > #
> > # A fatal error has been detected by the Java Runtime Environment:
> > #
> > #  Internal Error (assembler_aarch64.hpp:237), pid=2,
> tid=0xffffa0004109c630
> > #  guarantee(val < (1U << nbits)) failed: Field too big for insn
> > #
> > # JRE version:  (8.0_282-b08) (build )
> > # Java VM: OpenJDK 64-Bit Server VM (25.282-b08 mixed mode
> > linux-aarch64 compressed oops)
> > # Core dump written. Default location: //core or core.2
> > #
> > # An error report file with more information is saved as:
> > # /tmp/hs_err_pid2.log
> > #
> > # If you would like to submit a bug report, please visit:
> > #http://bugreport.java.com/bugreport/crash.jsp
>
> This looks like JDK-8247766
> (https://bugs.openjdk.java.net/browse/JDK-8247766), it has been fixed in
> 8u322.
>
> Thanks for the hint. I have tried JDK 8u322 and unfortunately, I still see
a similarly-looking crash:

"#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (assembler_aarch64.hpp:237), pid=2, tid=0xffffa00040b3e950
#  guarantee(val < (1U << nbits)) failed: Field too big for insn
#
# JRE version:  (8.0_322-b06) (build )
# Java VM: OpenJDK 64-Bit Server VM (25.322-b06 mixed mode linux-aarch64
compressed oops)
# Core dump written. Default location: //core or core.2
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid2.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues"

I did notice a comment in the description of JDK-8247766:
"Stack access code does not handle large offsets."

Does this mean that the JIT compiler would generate incorrect machine code
to access memory with PC-based offsets of something like this?

Thanks,
Waldek

For a full crash log please see an attachment.

>
> -Zhengyu
>
>
> > #
> > Aborted
> >
> > [backtrace]
> > 0x000010000097a750 <???+9938768>
> > 0x0000100000b90590 <???+12125584>
>
>