Immediately after starting to run / debug the project in Eclipse I am getting this fatal error:
objc[1032]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/bin/java and /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined. [INFO] Scanning for projects… [INFO] [INFO] ———————————————————————— [INFO] Building test-share AMP project 1.0-SNAPSHOT [INFO] ———————————————————————— # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00000001054e41cf, pid=1032, tid=20227 # # JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode bsd-amd64 compressed oops) # Problematic frame: # V [libjvm.dylib+0xe41cf] # # 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/peter/alfresco-dev/test-share/hs_err_pid1032.log [thread 4867 also had an error] # # Compiler replay data is saved as: # /Users/peter/alfresco-dev/test-share/replay_pid1032.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp #
I have just installed a new Mac with El Capitan, Eclipse 4.5.0, jdk 8u60 and Maven 3.3.3 and I get the same SIGSEGV with a newly created all-in-one project.
After quite a few hours of troubleshooting I managed to get it to work in Eclipse. It tuns out that all I had to do is change the "Maven Runtime" in the run configuration (see screenshot). This was set to "EMBEDDED 3.3.3", but changing that to my own downloaded version of 3.3.3.3 seems to have done the trick.
