Hi folks, I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too. ../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode) # An error report file with more information is saved as hs_err_pid97421.log # # Please submit bug reports to landonf@bikemonkey.org # Abort trap Thanks, Andrei # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode) # Please submit bug reports to landonf@bikemonkey.org # --------------- T H R E A D --------------- Current thread (0x00800800): JavaThread "main" [_thread_in_native, id=-1341845504] Stack: [0xb0001000,0xb0051000), sp=0xb004f3a0, free space=312k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [libjvm.dylib+0x3bef50] V [libjvm.dylib+0x14b06f] V [libjvm.dylib+0x3958d9] j sun.misc.Unsafe.registerNatives()V+0 j sun.misc.Unsafe.<clinit>()V+0 v ~StubRoutines::call_stub V [libjvm.dylib+0x1b6cc4] V [libjvm.dylib+0x2ef7a1] V [libjvm.dylib+0x1b5a63] V [libjvm.dylib+0x18b3cc] V [libjvm.dylib+0x18e79e] V [libjvm.dylib+0x18edf8] V [libjvm.dylib+0x2b5d65] V [libjvm.dylib+0x2b773b] V [libjvm.dylib+0x2b77fc] V [libjvm.dylib+0x1aae58] j java.util.concurrent.atomic.AtomicInteger.<clinit>()V+0 v ~StubRoutines::call_stub V [libjvm.dylib+0x1b6cc4] V [libjvm.dylib+0x2ef7a1] V [libjvm.dylib+0x1b5a63] V [libjvm.dylib+0x18b3cc] V [libjvm.dylib+0x18e79e] V [libjvm.dylib+0x18edf8] V [libjvm.dylib+0x1a7cb3] j java.lang.ThreadLocal.<clinit>()V+0 v ~StubRoutines::call_stub V [libjvm.dylib+0x1b6cc4] V [libjvm.dylib+0x2ef7a1] V [libjvm.dylib+0x1b5a63] V [libjvm.dylib+0x18b3cc] V [libjvm.dylib+0x18e79e] V [libjvm.dylib+0x18edf8] V [libjvm.dylib+0x1a7cb3] j java.io.FileInputStream.<clinit>()V+0 v ~StubRoutines::call_stub V [libjvm.dylib+0x1b6cc4] V [libjvm.dylib+0x2ef7a1] V [libjvm.dylib+0x1b5a63] V [libjvm.dylib+0x18b3cc] V [libjvm.dylib+0x18e79e] V [libjvm.dylib+0x18edf8] V [libjvm.dylib+0x1a7cb3] j java.lang.System.initializeSystemClass()V+23 v ~StubRoutines::call_stub V [libjvm.dylib+0x1b6cc4] V [libjvm.dylib+0x2ef7a1] V [libjvm.dylib+0x1b66ef] V [libjvm.dylib+0x1b68d4] V [libjvm.dylib+0x3883ce] V [libjvm.dylib+0x1c0cff] C [javac+0x3832] AddOption+0x1773 C [javac+0x165f] JavaMain+0x88 C [libSystem.B.dylib+0x32155] _pthread_start+0x141 C [libSystem.B.dylib+0x32012] thread_start+0x22 Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) j sun.misc.Unsafe.registerNatives()V+0 j sun.misc.Unsafe.<clinit>()V+0 v ~StubRoutines::call_stub j java.util.concurrent.atomic.AtomicInteger.<clinit>()V+0 v ~StubRoutines::call_stub j java.lang.ThreadLocal.<clinit>()V+0 v ~StubRoutines::call_stub j java.io.FileInputStream.<clinit>()V+0 v ~StubRoutines::call_stub j java.lang.System.initializeSystemClass()V+23 v ~StubRoutines::call_stub --------------- P R O C E S S --------------- Java Threads: ( => current thread ) 0x00822000 JavaThread "Finalizer" daemon [_thread_blocked, id=-1340641280] 0x0081e000 JavaThread "Reference Handler" daemon [_thread_blocked, id=-1340977152] =>0x00800800 JavaThread "main" [_thread_in_native, id=-1341845504] Other Threads: 0x0081a000 VMThread [id=-1341313024] VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None Heap def new generation total 960K, used 17K [0x03960000, 0x03a60000, 0x03e40000) eden space 896K, 2% used [0x03960000, 0x039647c0, 0x03a40000) from space 64K, 0% used [0x03a40000, 0x03a40000, 0x03a50000) to space 64K, 0% used [0x03a50000, 0x03a50000, 0x03a60000) tenured generation total 7168K, used 0K [0x03e40000, 0x04540000, 0x07960000) the space 7168K, 0% used [0x03e40000, 0x03e40000, 0x03e40200, 0x04540000) compacting perm gen total 12288K, used 783K [0x07960000, 0x08560000, 0x0b960000) the space 12288K, 6% used [0x07960000, 0x07a23fb0, 0x07a24000, 0x08560000) No shared spaces configured. Dynamic libraries: 0x00000000 /usr/lib/libgcc_s.1.dylib 0x00000000 /usr/lib/libSystem.B.dylib 0x00000000 /usr/lib/system/libmathCommon.A.dylib 0x01000000 /Users/dav/bsd-port/bsd-port-29/build/bsd-i586/lib/i386/client/libjvm.dylib 0x00000000 /usr/lib/libstdc++.6.dylib 0x00028000 /Users/dav/bsd-port/bsd-port-29/build/bsd-i586/lib/i386/native_threads/libhpi.dylib 0x0003f000 /Users/dav/bsd-port/bsd-port-29/build/bsd-i586/lib/i386/libverify.dylib 0x00051000 /Users/dav/bsd-port/bsd-port-29/build/bsd-i586/lib/i386/libjava.dylib 0x0008b000 /Users/dav/bsd-port/bsd-port-29/build/bsd-i586/lib/i386/libzip.dylib VM Arguments: jvm_args: -Dapplication.home=/Users/dav/bsd-port/bsd-port-29/build/bsd-i586 -Xms8m java_command: com.sun.tools.javac.Main Launcher Type: SUN_STANDARD Environment Variables: PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin SHELL=/bin/bash DISPLAY=/tmp/launch-hdtWLK/:0 DYLD_FALLBACK_LIBRARY_PATH=/Users/dav/bsd-port/bsd-port-29/build/bsd-i586/lib/i386/client:/Users/dav/bsd-port/bsd-port-29/build/bsd-i586/lib/i386:/Users/dav/bsd-port/bsd-port-29/build/bsd-i586/../lib/i386 Signal Handlers: SIGSEGV: [libjvm.dylib+0x3bfba0], sa_mask[0]=0xfffefeff, sa_flags=0x00000042 SIGBUS: [libjvm.dylib+0x3bfba0], sa_mask[0]=0xfffefeff, sa_flags=0x00000042 SIGFPE: [libjvm.dylib+0x2ef550], sa_mask[0]=0xfffefeff, sa_flags=0x00000042 SIGPIPE: [libjvm.dylib+0x2ef550], sa_mask[0]=0xfffefeff, sa_flags=0x00000042 SIGILL: [libjvm.dylib+0x2ef550], sa_mask[0]=0xfffefeff, sa_flags=0x00000042 SIGUSR1: SIG_DFL, sa_mask[0]=0x63807efb, sa_flags=0x00000000 SIGUSR2: [libjvm.dylib+0x2f0740], sa_mask[0]=0x00000000, sa_flags=0x00000042 SIGHUP: SIG_DFL, sa_mask[0]=0x63807efb, sa_flags=0x00000000 SIGINT: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000 SIGQUIT: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000 SIGTERM: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000 SIGUSR2: [libjvm.dylib+0x2f0740], sa_mask[0]=0x00000000, sa_flags=0x00000042 --------------- S Y S T E M --------------- OS:Bsd uname:Darwin 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386 i386 rlimit: STACK 8192k, CORE 0k, NPROC 266, NOFILE 10240 CPU:total 2 (2 cores per cpu, 1 threads per core) family 6 model 7 stepping 6, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3 Memory: 4k page, physical 1845244k(461311k free) vm_info: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00) for bsd-x86, built on Aug 19 2008 14:59:13 by "landonf" with gcc 4.0.1 (Apple Inc. build 5484)
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode) ^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei, That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH? ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X: http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html Regards, -Kurt
Kurt, yep, I used these variables since that time because noticed that they don't really affect the build process itself - I got some binaries and never tried how they work. Now I see that variables... do affect JDK somehow. :( So here is the script: -------------------------------- #!/bin/bash export ALT_BOOTDIR=/export/devtools/binary.plugs/soylatte16-i386-1.0.3/ export ANT_HOME=/usr/share/ant export NO_DOCS=true export HOTSPOT_BUILD_JOBS=1; export ALT_FREETYPE_HEADERS_PATH=/usr/X11R6/include; export ALT_FREETYPE_LIB_PATH=/usr/X11R6/lib; export ALT_JIBX_LIBS_PATH=/export/devtools/jibx/lib/ log=bsdport.build.log time -p make VARIANT=DBG $* 2>&1 | tee $log -------------------------------- and it leads to the same error: make[7]: `/Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/../generated/sa-jdi.jar' is up to date. make[6]: `incls/_precompiled.incl.gch' is up to date. if [ -d /Users/dav/bsd-port-reference/hotspot/agent -a "x86" != "ia64" ] ; then \ make -f vm.make libsaproc.dylib; \ fi make[7]: `libsaproc.dylib' is up to date. All done. cd bsd_i486_compiler2/product && ./test_gamma java full version "1.6.0_03-p3-landonf_19_aug_2008_14_55-b00" # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00e8d50f, pid=40704, tid=2685097760 # # JRE version: 6.0_03 # Java VM: OpenJDK Server VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0xb150f] # # An error report file with more information is saved as: # /Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/hs_err_pid40704.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ./test_gamma: line 12: 40704 Abort trap ./${gamma:-gamma} -Xbatch -showversion Queens < /dev/null make[4]: *** [product] Error 134 make[3]: *** [generic_build2] Error 2 make[2]: *** [product] Error 2 make[1]: *** [hotspot-build] Error 2 make: *** [build_product_image] Error 2 real 41.36 user 32.39 sys 15.49 Also verified that JAVA_HOME, ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH not set. I'm building from the bsd-port/ and bsd-port/hotspot/ folders with similar results listed above. :( Thanks, Andrei Kurt Miller wrote:
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode)
^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei,
That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH?
ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X:
http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html
Regards, -Kurt
Hi Andrei, Hmm, it would be helpful to do a debug build. I see you used VARIANT=DBG, but doesn't appear to be working as expected. Can you rebuild with this for your last line of the script? time -p make debug_build $* 2>&1 | tee $log That will get some debug info into libjvm.dylib and hopefully we can see the function and line number that is crashing. Regards, -Kurt Andrei Dmitriev wrote:
Kurt,
yep, I used these variables since that time because noticed that they don't really affect the build process itself - I got some binaries and never tried how they work. Now I see that variables... do affect JDK somehow. :( So here is the script: -------------------------------- #!/bin/bash
export ALT_BOOTDIR=/export/devtools/binary.plugs/soylatte16-i386-1.0.3/ export ANT_HOME=/usr/share/ant export NO_DOCS=true export HOTSPOT_BUILD_JOBS=1; export ALT_FREETYPE_HEADERS_PATH=/usr/X11R6/include; export ALT_FREETYPE_LIB_PATH=/usr/X11R6/lib; export ALT_JIBX_LIBS_PATH=/export/devtools/jibx/lib/
log=bsdport.build.log
time -p make VARIANT=DBG $* 2>&1 | tee $log -------------------------------- and it leads to the same error:
make[7]: `/Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/../generated/sa-jdi.jar' is up to date. make[6]: `incls/_precompiled.incl.gch' is up to date. if [ -d /Users/dav/bsd-port-reference/hotspot/agent -a "x86" != "ia64" ] ; then \ make -f vm.make libsaproc.dylib; \ fi make[7]: `libsaproc.dylib' is up to date. All done. cd bsd_i486_compiler2/product && ./test_gamma java full version "1.6.0_03-p3-landonf_19_aug_2008_14_55-b00" # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00e8d50f, pid=40704, tid=2685097760 # # JRE version: 6.0_03 # Java VM: OpenJDK Server VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0xb150f] # # An error report file with more information is saved as: # /Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/hs_err_pid40704.log
# # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ./test_gamma: line 12: 40704 Abort trap ./${gamma:-gamma} -Xbatch -showversion Queens < /dev/null make[4]: *** [product] Error 134 make[3]: *** [generic_build2] Error 2 make[2]: *** [product] Error 2 make[1]: *** [hotspot-build] Error 2 make: *** [build_product_image] Error 2 real 41.36 user 32.39 sys 15.49
Also verified that JAVA_HOME, ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH not set. I'm building from the bsd-port/ and bsd-port/hotspot/ folders with similar results listed above. :(
Thanks, Andrei
Kurt Miller wrote:
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode)
^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei,
That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH?
ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X:
http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html
Regards, -Kurt
On Mon, Jun 29, 2009 at 03:59:28PM -0400, Kurt Miller wrote:
Hi Andrei,
Hmm, it would be helpful to do a debug build. I see you used VARIANT=DBG, but doesn't appear to be working as expected. Can you rebuild with this for your last line of the script?
time -p make debug_build $* 2>&1 | tee $log
That will get some debug info into libjvm.dylib and hopefully we can see the function and line number that is crashing.
FWIW, pulling in last night's update would be a sensible first step then so that the debug info will correspond to the current source. There is also a small chance that the bug will have been fixed by the sync.
Andrei Dmitriev wrote:
Kurt,
yep, I used these variables since that time because noticed that they don't really affect the build process itself - I got some binaries and never tried how they work. Now I see that variables... do affect JDK somehow. :( So here is the script: -------------------------------- #!/bin/bash
export ALT_BOOTDIR=/export/devtools/binary.plugs/soylatte16-i386-1.0.3/ export ANT_HOME=/usr/share/ant export NO_DOCS=true export HOTSPOT_BUILD_JOBS=1; export ALT_FREETYPE_HEADERS_PATH=/usr/X11R6/include; export ALT_FREETYPE_LIB_PATH=/usr/X11R6/lib; export ALT_JIBX_LIBS_PATH=/export/devtools/jibx/lib/
log=bsdport.build.log
time -p make VARIANT=DBG $* 2>&1 | tee $log -------------------------------- and it leads to the same error:
make[7]: `/Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/../generated/sa-jdi.jar' is up to date. make[6]: `incls/_precompiled.incl.gch' is up to date. if [ -d /Users/dav/bsd-port-reference/hotspot/agent -a "x86" != "ia64" ] ; then \ make -f vm.make libsaproc.dylib; \ fi make[7]: `libsaproc.dylib' is up to date. All done. cd bsd_i486_compiler2/product && ./test_gamma java full version "1.6.0_03-p3-landonf_19_aug_2008_14_55-b00" # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00e8d50f, pid=40704, tid=2685097760 # # JRE version: 6.0_03 # Java VM: OpenJDK Server VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0xb150f] # # An error report file with more information is saved as: # /Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/hs_err_pid40704.log
# # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ./test_gamma: line 12: 40704 Abort trap ./${gamma:-gamma} -Xbatch -showversion Queens < /dev/null make[4]: *** [product] Error 134 make[3]: *** [generic_build2] Error 2 make[2]: *** [product] Error 2 make[1]: *** [hotspot-build] Error 2 make: *** [build_product_image] Error 2 real 41.36 user 32.39 sys 15.49
Also verified that JAVA_HOME, ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH not set. I'm building from the bsd-port/ and bsd-port/hotspot/ folders with similar results listed above. :(
Thanks, Andrei
Kurt Miller wrote:
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode)
^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei,
That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH?
ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X:
http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html
Regards, -Kurt
-- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org
Hi Greg, thanks for the idea! I verified that I have latest source... Seem we found the reason now - seem hotspot has never actually built because of some g++ specifics so it just picked soylatte up as a binary or as a library. Thanks! Andrei Greg Lewis wrote:
On Mon, Jun 29, 2009 at 03:59:28PM -0400, Kurt Miller wrote:
Hi Andrei,
Hmm, it would be helpful to do a debug build. I see you used VARIANT=DBG, but doesn't appear to be working as expected. Can you rebuild with this for your last line of the script?
time -p make debug_build $* 2>&1 | tee $log
That will get some debug info into libjvm.dylib and hopefully we can see the function and line number that is crashing.
FWIW, pulling in last night's update would be a sensible first step then so that the debug info will correspond to the current source. There is also a small chance that the bug will have been fixed by the sync.
Andrei Dmitriev wrote:
Kurt,
yep, I used these variables since that time because noticed that they don't really affect the build process itself - I got some binaries and never tried how they work. Now I see that variables... do affect JDK somehow. :( So here is the script: -------------------------------- #!/bin/bash
export ALT_BOOTDIR=/export/devtools/binary.plugs/soylatte16-i386-1.0.3/ export ANT_HOME=/usr/share/ant export NO_DOCS=true export HOTSPOT_BUILD_JOBS=1; export ALT_FREETYPE_HEADERS_PATH=/usr/X11R6/include; export ALT_FREETYPE_LIB_PATH=/usr/X11R6/lib; export ALT_JIBX_LIBS_PATH=/export/devtools/jibx/lib/
log=bsdport.build.log
time -p make VARIANT=DBG $* 2>&1 | tee $log -------------------------------- and it leads to the same error:
make[7]: `/Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/../generated/sa-jdi.jar' is up to date. make[6]: `incls/_precompiled.incl.gch' is up to date. if [ -d /Users/dav/bsd-port-reference/hotspot/agent -a "x86" != "ia64" ] ; then \ make -f vm.make libsaproc.dylib; \ fi make[7]: `libsaproc.dylib' is up to date. All done. cd bsd_i486_compiler2/product && ./test_gamma java full version "1.6.0_03-p3-landonf_19_aug_2008_14_55-b00" # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00e8d50f, pid=40704, tid=2685097760 # # JRE version: 6.0_03 # Java VM: OpenJDK Server VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0xb150f] # # An error report file with more information is saved as: # /Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/hs_err_pid40704.log
# # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ./test_gamma: line 12: 40704 Abort trap ./${gamma:-gamma} -Xbatch -showversion Queens < /dev/null make[4]: *** [product] Error 134 make[3]: *** [generic_build2] Error 2 make[2]: *** [product] Error 2 make[1]: *** [hotspot-build] Error 2 make: *** [build_product_image] Error 2 real 41.36 user 32.39 sys 15.49
Also verified that JAVA_HOME, ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH not set. I'm building from the bsd-port/ and bsd-port/hotspot/ folders with similar results listed above. :(
Thanks, Andrei
Kurt Miller wrote:
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode)
^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei,
That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH?
ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X:
http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html
Regards, -Kurt
Well, I meant that the build itself is crashing with the error below... :( Also just verified that I have a fresh bsd repo with latest merge with the main OpenJDK: The thing is that if I change the variant to debug_build then the following compile-time error occur: In file included from ../generated/incls/_ad_x86_32.cpp.incl:1, from ../generated/adfiles/ad_x86_32.cpp:29: ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosINode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4534: error: 'Op_CountLeadingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosI_bsrNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4558: error: 'Op_CountLeadingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosLNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4582: error: 'Op_CountLeadingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosL_bsrNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4607: error: 'Op_CountLeadingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countTrailingZerosINode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4632: error: 'Op_CountTrailingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countTrailingZerosLNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4656: error: 'Op_CountTrailingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.cpp: At global scope: ../generated/adfiles/ad_x86_32.cpp:1079: error: no 'const bool Matcher::match_rule_supported(int)' member function declared in class 'Matcher' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosINode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8642: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosI_bsrNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8660: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosLNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8684: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp:8686: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosL_bsrNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8708: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp:8713: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countTrailingZerosINode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8735: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countTrailingZerosLNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8758: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp:8760: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp: At global scope: ../generated/adfiles/ad_x86_32.cpp:22955: error: too many initializers for 'const bool [310]' make[7]: *** [ad_x86_32.o] Error 1 make[6]: *** [the_vm] Error 2 make[5]: *** [jvmg] Error 2 make[4]: *** [generic_build2] Error 2 make[3]: *** [jvmg] Error 2 make[2]: *** [hotspot-build] Error 2 make[1]: *** [generic_debug_build] Error 2 make: *** [build_debug_image] Error 2 real 61.52 user 31.24 sys 17.23 Suspecting that g++ causing this I tried g++4.0.1 (I upgraded the compiler to 4.2 some time ago for some purpose...) and that was the reason so at least java/javac are now built and I could compile a test and show some GUI now. Thanks, Andrei Kurt Miller wrote:
Hi Andrei,
Hmm, it would be helpful to do a debug build. I see you used VARIANT=DBG, but doesn't appear to be working as expected. Can you rebuild with this for your last line of the script?
time -p make debug_build $* 2>&1 | tee $log
That will get some debug info into libjvm.dylib and hopefully we can see the function and line number that is crashing.
Regards, -Kurt
Andrei Dmitriev wrote:
Kurt,
yep, I used these variables since that time because noticed that they don't really affect the build process itself - I got some binaries and never tried how they work. Now I see that variables... do affect JDK somehow. :( So here is the script: -------------------------------- #!/bin/bash
export ALT_BOOTDIR=/export/devtools/binary.plugs/soylatte16-i386-1.0.3/ export ANT_HOME=/usr/share/ant export NO_DOCS=true export HOTSPOT_BUILD_JOBS=1; export ALT_FREETYPE_HEADERS_PATH=/usr/X11R6/include; export ALT_FREETYPE_LIB_PATH=/usr/X11R6/lib; export ALT_JIBX_LIBS_PATH=/export/devtools/jibx/lib/
log=bsdport.build.log
time -p make VARIANT=DBG $* 2>&1 | tee $log -------------------------------- and it leads to the same error:
make[7]: `/Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/../generated/sa-jdi.jar' is up to date. make[6]: `incls/_precompiled.incl.gch' is up to date. if [ -d /Users/dav/bsd-port-reference/hotspot/agent -a "x86" != "ia64" ] ; then \ make -f vm.make libsaproc.dylib; \ fi make[7]: `libsaproc.dylib' is up to date. All done. cd bsd_i486_compiler2/product && ./test_gamma java full version "1.6.0_03-p3-landonf_19_aug_2008_14_55-b00" # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00e8d50f, pid=40704, tid=2685097760 # # JRE version: 6.0_03 # Java VM: OpenJDK Server VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0xb150f] # # An error report file with more information is saved as: # /Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/hs_err_pid40704.log
# # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ./test_gamma: line 12: 40704 Abort trap ./${gamma:-gamma} -Xbatch -showversion Queens < /dev/null make[4]: *** [product] Error 134 make[3]: *** [generic_build2] Error 2 make[2]: *** [product] Error 2 make[1]: *** [hotspot-build] Error 2 make: *** [build_product_image] Error 2 real 41.36 user 32.39 sys 15.49
Also verified that JAVA_HOME, ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH not set. I'm building from the bsd-port/ and bsd-port/hotspot/ folders with similar results listed above. :(
Thanks, Andrei
Kurt Miller wrote:
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode)
^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei,
That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH?
ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X:
http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html
Regards, -Kurt
Hi Andrei, If I understand your email correctly: 1) bsd-port will not build with gcc 4.2 due to the below compiler error 2) bsd-port builds fine using soylatte with gcc 4.0.1 on MacOSX and appears to work fine to 3) The previous build crashes were due to env vars or other issues which are no longer a problem. Does that summarize the current state correctly? Regards, -Kurt Andrei Dmitriev wrote:
Well, I meant that the build itself is crashing with the error below... :(
Also just verified that I have a fresh bsd repo with latest merge with the main OpenJDK:
The thing is that if I change the variant to debug_build then the following compile-time error occur: In file included from ../generated/incls/_ad_x86_32.cpp.incl:1, from ../generated/adfiles/ad_x86_32.cpp:29: ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosINode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4534: error: 'Op_CountLeadingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosI_bsrNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4558: error: 'Op_CountLeadingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosLNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4582: error: 'Op_CountLeadingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosL_bsrNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4607: error: 'Op_CountLeadingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countTrailingZerosINode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4632: error: 'Op_CountTrailingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countTrailingZerosLNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4656: error: 'Op_CountTrailingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.cpp: At global scope: ../generated/adfiles/ad_x86_32.cpp:1079: error: no 'const bool Matcher::match_rule_supported(int)' member function declared in class 'Matcher' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosINode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8642: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosI_bsrNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8660: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosLNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8684: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp:8686: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosL_bsrNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8708: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp:8713: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countTrailingZerosINode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8735: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countTrailingZerosLNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8758: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp:8760: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp: At global scope: ../generated/adfiles/ad_x86_32.cpp:22955: error: too many initializers for 'const bool [310]' make[7]: *** [ad_x86_32.o] Error 1 make[6]: *** [the_vm] Error 2 make[5]: *** [jvmg] Error 2 make[4]: *** [generic_build2] Error 2 make[3]: *** [jvmg] Error 2 make[2]: *** [hotspot-build] Error 2 make[1]: *** [generic_debug_build] Error 2 make: *** [build_debug_image] Error 2 real 61.52 user 31.24 sys 17.23
Suspecting that g++ causing this I tried g++4.0.1 (I upgraded the compiler to 4.2 some time ago for some purpose...) and that was the reason so at least java/javac are now built and I could compile a test and show some GUI now.
Thanks, Andrei
Kurt Miller wrote:
Hi Andrei,
Hmm, it would be helpful to do a debug build. I see you used VARIANT=DBG, but doesn't appear to be working as expected. Can you rebuild with this for your last line of the script?
time -p make debug_build $* 2>&1 | tee $log
That will get some debug info into libjvm.dylib and hopefully we can see the function and line number that is crashing.
Regards, -Kurt
Andrei Dmitriev wrote:
Kurt,
yep, I used these variables since that time because noticed that they don't really affect the build process itself - I got some binaries and never tried how they work. Now I see that variables... do affect JDK somehow. :( So here is the script: -------------------------------- #!/bin/bash
export ALT_BOOTDIR=/export/devtools/binary.plugs/soylatte16-i386-1.0.3/ export ANT_HOME=/usr/share/ant export NO_DOCS=true export HOTSPOT_BUILD_JOBS=1; export ALT_FREETYPE_HEADERS_PATH=/usr/X11R6/include; export ALT_FREETYPE_LIB_PATH=/usr/X11R6/lib; export ALT_JIBX_LIBS_PATH=/export/devtools/jibx/lib/
log=bsdport.build.log
time -p make VARIANT=DBG $* 2>&1 | tee $log -------------------------------- and it leads to the same error:
make[7]: `/Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/../generated/sa-jdi.jar'
is up to date. make[6]: `incls/_precompiled.incl.gch' is up to date. if [ -d /Users/dav/bsd-port-reference/hotspot/agent -a "x86" != "ia64" ] ; then \ make -f vm.make libsaproc.dylib; \ fi make[7]: `libsaproc.dylib' is up to date. All done. cd bsd_i486_compiler2/product && ./test_gamma java full version "1.6.0_03-p3-landonf_19_aug_2008_14_55-b00" # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00e8d50f, pid=40704, tid=2685097760 # # JRE version: 6.0_03 # Java VM: OpenJDK Server VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0xb150f] # # An error report file with more information is saved as: # /Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/hs_err_pid40704.log
# # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ./test_gamma: line 12: 40704 Abort trap ./${gamma:-gamma} -Xbatch -showversion Queens < /dev/null make[4]: *** [product] Error 134 make[3]: *** [generic_build2] Error 2 make[2]: *** [product] Error 2 make[1]: *** [hotspot-build] Error 2 make: *** [build_product_image] Error 2 real 41.36 user 32.39 sys 15.49
Also verified that JAVA_HOME, ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH not set. I'm building from the bsd-port/ and bsd-port/hotspot/ folders with similar results listed above. :(
Thanks, Andrei
Kurt Miller wrote:
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode)
^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei,
That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH?
ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X:
http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html
Regards, -Kurt
Hi Kurt, Kurt Miller wrote:
Hi Andrei,
If I understand your email correctly:
1) bsd-port will not build with gcc 4.2 due to the below compiler error
Correct.
2) bsd-port builds fine using soylatte with gcc 4.0.1 on MacOSX and appears to work fine to
Correct.
3) The previous build crashes were due to env vars or other issues which are no longer a problem.
Yes, that happened because of env. variables and g++ 4.2. Thanks, Andrei
Does that summarize the current state correctly?
Regards, -Kurt
Andrei Dmitriev wrote:
Well, I meant that the build itself is crashing with the error below... :(
Also just verified that I have a fresh bsd repo with latest merge with the main OpenJDK:
The thing is that if I change the variant to debug_build then the following compile-time error occur: In file included from ../generated/incls/_ad_x86_32.cpp.incl:1, from ../generated/adfiles/ad_x86_32.cpp:29: ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosINode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4534: error: 'Op_CountLeadingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosI_bsrNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4558: error: 'Op_CountLeadingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosLNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4582: error: 'Op_CountLeadingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countLeadingZerosL_bsrNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4607: error: 'Op_CountLeadingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countTrailingZerosINode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4632: error: 'Op_CountTrailingZerosI' was not declared in this scope ../generated/adfiles/ad_x86_32.hpp: In member function 'virtual int countTrailingZerosLNode::ideal_Opcode() const': ../generated/adfiles/ad_x86_32.hpp:4656: error: 'Op_CountTrailingZerosL' was not declared in this scope ../generated/adfiles/ad_x86_32.cpp: At global scope: ../generated/adfiles/ad_x86_32.cpp:1079: error: no 'const bool Matcher::match_rule_supported(int)' member function declared in class 'Matcher' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosINode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8642: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosI_bsrNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8660: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosLNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8684: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp:8686: error: 'class MacroAssembler' has no member named 'lzcntl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countLeadingZerosL_bsrNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8708: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp:8713: error: 'class MacroAssembler' has no member named 'bsrl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countTrailingZerosINode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8735: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp: In member function 'virtual void countTrailingZerosLNode::emit(CodeBuffer&, PhaseRegAlloc*) const': ../generated/adfiles/ad_x86_32.cpp:8758: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp:8760: error: 'class MacroAssembler' has no member named 'bsfl' ../generated/adfiles/ad_x86_32.cpp: At global scope: ../generated/adfiles/ad_x86_32.cpp:22955: error: too many initializers for 'const bool [310]' make[7]: *** [ad_x86_32.o] Error 1 make[6]: *** [the_vm] Error 2 make[5]: *** [jvmg] Error 2 make[4]: *** [generic_build2] Error 2 make[3]: *** [jvmg] Error 2 make[2]: *** [hotspot-build] Error 2 make[1]: *** [generic_debug_build] Error 2 make: *** [build_debug_image] Error 2 real 61.52 user 31.24 sys 17.23
Suspecting that g++ causing this I tried g++4.0.1 (I upgraded the compiler to 4.2 some time ago for some purpose...) and that was the reason so at least java/javac are now built and I could compile a test and show some GUI now.
Thanks, Andrei
Kurt Miller wrote:
Hi Andrei,
Hmm, it would be helpful to do a debug build. I see you used VARIANT=DBG, but doesn't appear to be working as expected. Can you rebuild with this for your last line of the script?
time -p make debug_build $* 2>&1 | tee $log
That will get some debug info into libjvm.dylib and hopefully we can see the function and line number that is crashing.
Regards, -Kurt
Andrei Dmitriev wrote:
Kurt,
yep, I used these variables since that time because noticed that they don't really affect the build process itself - I got some binaries and never tried how they work. Now I see that variables... do affect JDK somehow. :( So here is the script: -------------------------------- #!/bin/bash
export ALT_BOOTDIR=/export/devtools/binary.plugs/soylatte16-i386-1.0.3/ export ANT_HOME=/usr/share/ant export NO_DOCS=true export HOTSPOT_BUILD_JOBS=1; export ALT_FREETYPE_HEADERS_PATH=/usr/X11R6/include; export ALT_FREETYPE_LIB_PATH=/usr/X11R6/lib; export ALT_JIBX_LIBS_PATH=/export/devtools/jibx/lib/
log=bsdport.build.log
time -p make VARIANT=DBG $* 2>&1 | tee $log -------------------------------- and it leads to the same error:
make[7]: `/Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/../generated/sa-jdi.jar'
is up to date. make[6]: `incls/_precompiled.incl.gch' is up to date. if [ -d /Users/dav/bsd-port-reference/hotspot/agent -a "x86" != "ia64" ] ; then \ make -f vm.make libsaproc.dylib; \ fi make[7]: `libsaproc.dylib' is up to date. All done. cd bsd_i486_compiler2/product && ./test_gamma java full version "1.6.0_03-p3-landonf_19_aug_2008_14_55-b00" # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0xa) at pc=0x00e8d50f, pid=40704, tid=2685097760 # # JRE version: 6.0_03 # Java VM: OpenJDK Server VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0xb150f] # # An error report file with more information is saved as: # /Users/dav/bsd-port-reference/build/bsd-i586/hotspot/outputdir/bsd_i486_compiler2/product/hs_err_pid40704.log
# # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # ./test_gamma: line 12: 40704 Abort trap ./${gamma:-gamma} -Xbatch -showversion Queens < /dev/null make[4]: *** [product] Error 134 make[3]: *** [generic_build2] Error 2 make[2]: *** [product] Error 2 make[1]: *** [hotspot-build] Error 2 make: *** [build_product_image] Error 2 real 41.36 user 32.39 sys 15.49
Also verified that JAVA_HOME, ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH not set. I'm building from the bsd-port/ and bsd-port/hotspot/ folders with similar results listed above. :(
Thanks, Andrei
Kurt Miller wrote:
Andrei Dmitriev wrote:
Hi folks,
I'm experiencing a crash with the latest javac and java build on MacOSX: Any ideas what's going on there? I think it's not an issue with the latest merge because I've seen that crash that week too.
../build/bsd-i586/bin/javac # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (554E534146450E43505004DA), pid=97421, tid=0xb0051000 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-p3-landonf_19_aug_2008_14_55-b00 mixed mode)
^^^^^^^^^^^^^^^^^^^^^^
Hi Andrei,
That looks like the soylatte hotspot not the bsd-port/openjdk7 hotspot. Did you build with ALT_HOTSPOT_IMPORT_PATH?
ALT_HOTSPOT_IMPORT_PATH and ALT_JDK_IMPORT_PATH can not point to a soylatte build. Leave them unset to build bsd-port. See the following email for an example of how to get a clean build of bsd-port on OS X:
http://mail.openjdk.java.net/pipermail/bsd-port-dev/2009-June/000735.html
Regards, -Kurt
Christian Thalinger wrote:
Andrei V. Dmitriev wrote:
1) bsd-port will not build with gcc 4.2 due to the below compiler error
Correct.
The error is related to stuff I have commited recently. Was this a clean build?
A clean HotSpot debug build with Apple's GCC 4.2: $ g++-4.2 --version i686-apple-darwin9-g++-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5574) worked for me. Although the built binary does not. -- Christian
Hi Christian, yes, it was a clean build. Actually I experienced two different things: 1) with ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH set *and* g++4.2 I've seen finished build but binaries crashed. 2) with ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH UNset *and* g++4.2 I got crash during the build. Though the crash log looks very similar in 1) and 2). Anyway, without these env. variables and g++4.0 that works good. I could double-check with g++4.2 if needed. Thanks, Andrei Christian Thalinger wrote:
Christian Thalinger wrote:
Andrei V. Dmitriev wrote:
1) bsd-port will not build with gcc 4.2 due to the below compiler error
Correct.
The error is related to stuff I have commited recently. Was this a clean build?
A clean HotSpot debug build with Apple's GCC 4.2:
$ g++-4.2 --version i686-apple-darwin9-g++-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5574)
worked for me. Although the built binary does not.
-- Christian
Andrei V. Dmitriev wrote:
Hi Christian,
yes, it was a clean build. Actually I experienced two different things: 1) with ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH set *and* g++4.2 I've seen finished build but binaries crashed. 2) with ALT_HOTSPOT_IMPORT_PATH, ALT_JDK_IMPORT_PATH UNset *and* g++4.2 I got crash during the build. Though the crash log looks very similar in 1) and 2). Anyway, without these env. variables and g++4.0 that works good. I could double-check with g++4.2 if needed.
Seems Apple's GCC 4.2 is not very mature. No need to double check. -- Christian
participants (5)
-
Andrei Dmitriev
-
Andrei V. Dmitriev
-
Christian Thalinger
-
Greg Lewis
-
Kurt Miller