OpenJDK 8 Segfault on Startup
attie.grande at argentum-systems.co.uk
Wed Nov 28 18:33:55 UTC 2018
Ahem... I meant to say: (apologies)
I applied the patch from JDK-8194739  and things have sprung into life.
The patch from JDK-8202600  had no effect, but I'll be keeping it applied.
I've not yet tried JDK-8154210.
On Wed, 28 Nov 2018 at 18:28, Attie Grande
<attie.grande at argentum-systems.co.uk> wrote:
> Hi again Aleksey,
> I just wanted to say thanks ever so much for your input - linking me
> to JIRA, etc...
> I applied the patch from JDK-8154210  and things have sprung into life.
> I plan to submit this to the Yocto folks.
> : https://bugs.openjdk.java.net/browse/JDK-8154210
> : http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/3d7d041acb59
> On Wed, 28 Nov 2018 at 14:11, Aleksey Shipilev <ashipile at redhat.com> wrote:
> > On 11/28/18 12:34 AM, Attie Grande wrote:
> > > A fatal log is here:
> > > https://pastebin.com/raw/iXTz8v9z
> > >
> > > Output from a crash in gdb (still no symbols):
> > > https://pastebin.com/raw/dS8zak5H
> > >
> > > The content of siginfo_t... if it's helpful:
> > > https://pastebin.com/raw/hUwZPUUd
> > 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  is from Red Hat RPM integration repository , 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  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  for the error message, there are a few interesting hits
> > that have no backports to 8u162 . Both might be easy to apply to your current 8u tree .
> > (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?
> > -Aleksey
> > 
> > https://builds.shipilev.net/openjdk-jdk8-redhat/openjdk-jdk8-redhat-latest-linux-arm32-hflt-zero-fastdebug.tar.xz
> >  http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/
> >  https://bugs.openjdk.java.net/secure/QuickSearch.jspa?searchString=caught+unhandled+signal+11
> >  https://bugs.openjdk.java.net/browse/JDK-8194739
> >  https://bugs.openjdk.java.net/browse/JDK-8202600
> >  http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/8bd024c567e7
> >  http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/ca4663e58916
More information about the jdk-dev