GWT team asked me to report against Fedora. So I did.
[GWT compiler crash on Fedora 20]
I've had a few instances where the GWT compile did NOT finish and thus the oVirt build
failed. But simply re-running it works.
Greg
----- Original Message -----
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Greg Sheremeta" <gshereme(a)redhat.com>
Cc: "Adam Litke" <alitke(a)redhat.com>, "engine-devel"
<engine-devel(a)ovirt.org>
Sent: Friday, January 3, 2014 11:59:16 AM
Subject: Re: [Engine-devel] ovirt-engine build segfault on Fedora 20
this is probably native code bug in openjdk.
----- Original Message -----
> From: "Greg Sheremeta" <gshereme(a)redhat.com>
> To: "Adam Litke" <alitke(a)redhat.com>
> Cc: "engine-devel" <engine-devel(a)ovirt.org>
> Sent: Friday, January 3, 2014 6:55:05 PM
> Subject: Re: [Engine-devel] ovirt-engine build segfault on Fedora 20
>
>
>
> ----- Original Message -----
> > From: "Adam Litke" <alitke(a)redhat.com>
> > To: "Greg Sheremeta" <gshereme(a)redhat.com>
> > Cc: "engine-devel" <engine-devel(a)ovirt.org>
> > Sent: Friday, January 3, 2014 11:37:43 AM
> > Subject: Re: [Engine-devel] ovirt-engine build segfault on Fedora 20
> >
> > On 02/01/14 21:53 -0500, Greg Sheremeta wrote:
> > >Caution on upgrading your dev machine to Fedora 20. GWT compilation of
> > >"safari" (for Chrome) causes a segfault during the build.
Strangely, the
> > >build appears to work, so I'm not sure what the net effect of the
> > >segfault
> > >is.
> > >
> > >If you only compile for gecko (Firefox) [the default], you won't see
the
> > >segfault.
> > >
> > >In other words,
> > >make clean install-dev PREFIX=$HOME/ovirt-engine
> >
>DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=gecko1_8,safari"
> > >causes the segfault
> > >
> > >But
> > >make install-dev PREFIX="$HOME/ovirt-engine"
> > >works just fine.
> > >
> > >I've duplicated this with with both OpenJDK and Oracle JDK.
> >
> > I can confirm this on my F20 system with OpenJDK as well. So far I
> > have not observed any problems with the resulting build.
> >
> >
> I've since duplicated it building a different GWT project, so I'll report
> the
> bug against GWT.
>
> I also see a similar crash in Eclipse if Eclipse is using webkit (the
> default) AND Google Talk is installed. Either uninstalling GTalk or using
> -Dorg.eclipse.swt.browser.DefaultType=mozilla
> works around that. So the GWT bug might be a JDK bug. Thoughts?
>
> ...
>
> GWT compiling a different GWT project --->
>
> [INFO] Compiling module com.github.gwtbootstrap.Bootstrap
> [INFO] Compiling 6 permutations
> [INFO] Compiling permutation 0...
> [INFO] Compiling permutation 2...
> [INFO] Process output
> [INFO] Compiling
> [INFO] Compiling permutation 1...
> [INFO] Compiling permutation 3...
> [INFO] Compiling permutation 4...
> [INFO] Compiling permutation 5...
> [INFO] Compile of permutations succeeded
> *** Error in `java': double free or corruption (out): 0x00007eff24015d60
> ***
> ======= Backtrace: =========
> /lib64/libc.so.6[0x342ce75d9f]
> /lib64/libc.so.6[0x342ce7d098]
>
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre-abrt/lib/amd64/server/libjvm.so(+0x8dcc3b)[0x7eff2b9d6c3b]
>
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre-abrt/lib/amd64/server/libjvm.so(+0x5ce967)[0x7eff2b6c8967]
>
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.3.0.fc20.x86_64/jre-abrt/lib/amd64/server/libjvm.so(JVM_Halt+0x30)[0x7eff2b706b10]
> [0x7eff210135ec]
> ======= Memory map: ========
>
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/engine-devel
>