This appears to still be broken when I try and build. Has the change that caused this been identified? How do I sync back to before this happened with hg?
Thanks, Sam On Mar 9, 2011, at 9:02 AM, Stephen Bannasch wrote: > I'm using soylatte16-i386-1.0.3 and have backed out all my changes and John > Roses patches and am getting an abort trap after a > seemingly successful build: > > testing build: ./build/bsd-amd64/j2sdk-image/bin/java -version > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00000001020ea915, pid=10411, tid=4298117120 > # > # JRE version: 7.0 > # Java VM: OpenJDK 64-Bit Server VM (21.0-b03 mixed mode bsd-amd64 compressed > oops) > # Problematic frame: > # C [libjvm.dylib+0x463915] JVM_ArrayCopy+0x105 > # > # Failed to write core dump. Core dumps have been disabled. To enable core > dumping, try "ulimit -c unlimited" before starting > Java again > # > # An error report file with more information is saved as: > # /Users/stephen/dev/java/src/bsd/hs_err_pid10411.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > Abort trap > > More details here: https://gist.github.com/b6e70c49bf1ad8ed5e20 >
