Fail to build on windows 'g1ParScanThreadState.cpp'

Boaz Nahum boaznahum at gmail.com
Mon Nov 30 19:58:02 UTC 2015


Thank you every one. Now it works.

If you are interested, here is the crash report after attempting a simple
compilation(Worked in the past)
===Begin here ===================================================
Information:11/30/2015 7:52 PM - Compilation completed with 1 error and 0
warnings in 9ms
Error:Abnormal build process termination:
Build process started. Classpath:
/F:/Dev/Tools/IntelliJ/15c/15.0.1x/lib/jps-launcher.jar;F:/Dev/JDK8Build/valhalla/build/windows-x86_64-normal-server-release/images/jdk/lib/tools.jar;/F:/Dev/Tools/IntelliJ/15c/15.0.1x/lib/optimizedFileManager.jar;F:/Dev/Tools/IntelliJ/15c/15.0.1x/lib/ecj-4.4.jar
[thread 9596 also had an error][thread 11872 also had an error][thread 3644
also had an error]
[thread 2676 also had an error]
[thread 10700 also had an error]
[thread 7676 also had an error]
[thread 11040 also had an error]
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d187dc2,
pid=10548, tid=6568
#
# JRE version: OpenJDK Runtime Environment (9.0) (build
1.9.0-internal-boaz_2015_11_30_19_19-b00)
# Java VM: OpenJDK 64-Bit Server VM
(1.9.0-internal-boaz_2015_11_30_19_19-b00, mixed mode, tiered, compressed
oops, g1 gc, windows-amd64)
# Problematic frame:
# V  [jvm.dll+0x3e7dc2]#
# No core dump will be written. Minidumps are not enabled by default on
client versions of Windows
#
# An error report file with more information is saved as:
# F:\Dev\Tools\IntelliJ\15c\system\compile-server\hs_err_pid10548.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

===End here ===================================================

Boaz



On Mon, Nov 30, 2015 at 1:00 PM Maurizio Cimadamore <
maurizio.cimadamore at oracle.com> wrote:

> I've pushed the fix indicated by Volker (thanks!). Let me know if you
> see some improvements.
>
> Maurizio
>
> On 30/11/15 10:43, Maurizio Cimadamore wrote:
> >
> >
> > On 30/11/15 07:59, Volker Simonis wrote:
> >> If it's not there, you should just sync valhalla with the latest jdk9 or
> >> use VS2013 or newer.
> > Valhalla has been synced last week to jdk9 b93, so it should be fairly
> > recent. But it seems like this particular fix is very recent and
> > hasn't made it to b93.
> >
> > Maurizio
>
>


More information about the valhalla-dev mailing list