OpenJDK 8 Segfault on Startup

[Attie Grande]

For completeness, I have submitted patches to the meta-java Yocto team [1][2].

Thanks once again for your input.

[1]: http://lists.openembedded.org/pipermail/openembedded-devel/2018-November/197688.html
[2]: http://lists.openembedded.org/pipermail/openembedded-devel/2018-November/197689.html
On Wed, 28 Nov 2018 at 18:40, Aleksey Shipilev <ashipile at redhat.com> wrote:
>
> On 11/28/18 7:33 PM, Attie Grande wrote:
> > Ahem... I meant to say: (apologies)
> >
> > I applied the patch from JDK-8194739 [1][2] and things have sprung into life.
> >
> > The patch from JDK-8202600 [3][4] had no effect, but I'll be keeping it applied.
> > I've not yet tried JDK-8154210.
> >
> > Attie
> >
> > [1]: https://bugs.openjdk.java.net/browse/JDK-8194739
> > [2]: http://hg.openjdk.java.net/jdk/jdk10/rev/69d1a1590485
> > [3]: https://bugs.openjdk.java.net/browse/JDK-8202600
> > [4]: http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/ca4663e58916
>
> Thank God. I was running around screaming we somehow lost JDK-8154210 -- the issue there says it is
> in 8u121, so your 8u16{1,2} should include it. So that patch should not even apply to your tree.
>
> Here is the JDK-8194739 fix in 8u-style, tell Yocto people to include that to their patches until
> 8u17{1,2} is there for them?
>   http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/56123fdca84a
>
> JDK-8154210 is good to have as well, as it can spectacularly break at any moment with newer GCCs.
>
> -Aleksey
>