On Wed, Apr 8, 2009 at 4:06 PM, Brian E. Fox <[email protected]>wrote:
> The m2eclipse user list is more appropriate for this, but Igor found these > links: > http://www.mail-archive.com/[email protected]/msg728168.html > http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg21845.html > so it doesn't seem specific to M2e. > Updating to a more recent jre did the trick. Thanks for the pointers. Sean > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Sean > Davis > Sent: Wednesday, April 08, 2009 3:09 PM > To: [email protected] > Subject: m2eclipse and crashing on any access to pom.xml > > I am running eclipse under: > > > java -version > java version "1.6.0_04" > Java(TM) SE Runtime Environment (build 1.6.0_04-b12) > Java HotSpot(TM) 64-Bit Server VM (build 10.0-b19, mixed mode) > > When I do anything to add a dependency, I get a crash of the VM: > > # > # An unexpected error has been detected by Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00002adcdb63522a, pid=18211, tid=1085491536 > # > # Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b19 mixed mode > linux-amd64) > # Problematic frame: > # V [libjvm.so+0x1f122a] > # > # An error report file with more information is saved as: > # /home/sdavis/eclipse/hs_err_pid18211.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > > Any suggestions as to how to alleviate the problem? Do I really need to > back up to java 1.5 to use m2eclipse as some sites suggest? > > Thanks, > Sean >
