OpenJDK 8 Segfault on Startup

Aleksey Shipilev ashipile at
Wed Nov 28 14:11:36 UTC 2018

On 11/28/18 12:34 AM, Attie Grande wrote:
> A fatal log is here:
> Output from a crash in gdb (still no symbols):
> The content of siginfo_t... if it's helpful:

Okay, no help.

> PS: Thanks for trying the build on the RPi... that same build works
> fine on my board!
> Do you have any information on "what" was built? (i.e: patches,
> etc...) or is it built from vanilla 191-b12 sources?

Aha, interesting. That build [1] is from Red Hat RPM integration repository [2], which includes
latest upstream 8u, aarch64 port, and Shenandoah GC.

At this point, I have two hypotheses:

 a) Yocto patchset has a bad patch. It is a good thing the my build [1] runs, because it means glibc
is still functional on your board, which means you can probably build without any Yocto patches,
which opens up the opportunity to bisect.

 b) There is a bug/regression in Zero VM that was fixed in later 8u releases. Seeing that you build
8.0_162-b12, and searching through JIRA [3] for the error message, there are a few interesting hits
that have no backports to 8u162 [4][5]. Both might be easy to apply to your current 8u tree [6][7].
(Separately, you can see how the error in interpreter may lead to "surprise" SEGV originating from
Java code). Otherwise, try to update the tree to the latest 8u?



More information about the jdk-dev mailing list