Ok - i'm almost positive it is the same problem. I think the loadplugin thing is a misdirection. The project appears to crash compiling the code.
On Fri, Mar 27, 2009 at 3:59 PM, Vitali Lovich <vlov...@gmail.com> wrote: > Sorry - forgot to mention that this happened when I tried to load the > hosted mode browser. > > On Fri, Mar 27, 2009 at 3:57 PM, Vitali Lovich <vlov...@gmail.com> wrote: >> Might be related. Just set up my project to run under the regular >> hosted mode w/ 32-bit JVM: >> >> LoadPlugin: failed to initialize shared library >> /home/vlovich/.mozilla/plugins/libflashplayer.so >> [/home/vlovich/.mozilla/plugins/libflashplayer.so: wrong ELF class: >> ELFCLASS64] >> LoadPlugin: failed to initialize shared library >> /usr/lib/jvm/java-6-sunjre/lib/amd64/libnpjp2.so >> [/usr/lib/jvm/java-6-sunjre/lib/amd64/libnpjp2.so: wrong ELF class: >> ELFCLASS64] >> # >> # An unexpected error has been detected by Java Runtime Environment: >> # >> # SIGSEGV (0xb) at pc=0x0625665c, pid=20124, tid=3607796624 >> # >> # Java VM: Java HotSpot(TM) Server VM (10.0-b23 mixed mode linux-x86) >> # Problematic frame: >> # V [libjvm.so+0x25665c] >> # >> # An error report file with more information is saved as: >> # /home/vlovich/workspace/sacred_heart/hs_err_pid20124.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. >> # >> >> >> >> On Fri, Mar 27, 2009 at 3:07 PM, Vitali Lovich <vlov...@gmail.com> wrote: >>> You can also has the hs_err for the 32-bit vm >>> >>> On Fri, Mar 27, 2009 at 2:26 PM, Vitali Lovich <vlov...@gmail.com> wrote: >>>> Ugggh... you want me to do all the work don't you :D >>>> >>>> On a separate note 5094 compilation is broken (JUnitShell fails to >>>> compile). In 5096 the problem is resolved. >>>> >>>> On Fri, Mar 27, 2009 at 2:03 PM, Scott Blum <sco...@google.com> wrote: >>>>> >>>>> I can has hs_err_pid17105.log? >>>>> >>>>> On Fri, Mar 27, 2009 at 12:36 PM, Vitali Lovich <vlov...@gmail.com> wrote: >>>>>> >>>>>> [java] Compiling module com.google.gwt.benchmarks.viewer.ReportViewer >>>>>> [java] # >>>>>> [java] # An unexpected error has been detected by Java Runtime >>>>>> Environment: >>>>>> [java] # >>>>>> [java] # SIGSEGV (0xb) at pc=0x0625665c, pid=17105, tid=3762477968 >>>>>> [java] # >>>>>> [java] # Java VM: Java HotSpot(TM) Server VM (10.0-b23 mixed mode >>>>>> linux-x86) >>>>>> [java] # Problematic frame: >>>>>> [java] # V [libjvm.so+0x25665c] >>>>>> [java] # >>>>>> [java] # An error report file with more information is saved as: >>>>>> [java] # >>>>>> /home/vlovich/workspace/gwt/tools/benchmark-viewer/hs_err_pid17105.log >>>>>> [java] # >>>>>> [java] # If you would like to submit a bug report, please visit: >>>>>> [java] # http://java.sun.com/webapps/bugreport/crash.jsp >>>>>> [java] # The crash happened outside the Java Virtual Machine in >>>>>> native code. >>>>>> [java] # See problematic frame for where to report the bug. >>>>>> [java] # >>>>>> >>>>>> This is kind of annoying because GWT fails to build with the newer JDKs >>>>>> due to the issue mentioned before with the change to generics. So it's a >>>>>> two step workaround: Use the older sun JDK to compile the classes & >>>>>> after >>>>>> it crashes, use run ant again with the newer JDK so that the GWT compiler >>>>>> doesn't crash the VM. >>>>>> >>>>>> This also happens if I try to use the older JDK with my projects, but >>>>>> that's not really an issue since I just use the latest OpenJDK in the >>>>>> Ubuntu >>>>>> repos. >>>>>> >>>>>> Might be relevant that I'm using 64-bit jdks. >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
