Community
Participate
Working Groups
Build Identifier: 20110218-0911 A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0xb285b899, pid=2572, tid=3076044480 JRE version: 6.0_20-b02 Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing linux-x86 ) Problematic frame: C [UTF-16.so+0x899] gconv+0x3b9 An error report file with more information is saved as: /home/cquiros/eclipse/hs_err_pid2572.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. Reproducible: Always Steps to Reproduce: 1. Open the IDE 2. Open the project -- 3. Open the java source with errors
Created attachment 194124 [details] Crash log
Seems like some problem occured while creating the SWT browser control. Moving to Platform/SWT for comment
It's trying to use seamonkey-2.x, which is not a supported renderer. I'm not sure why it's trying this though. Questions: - which linux distro/version are you using? - is /usr/lib/seamonkey/ a link to /usr/lib/seamonkey-2.0.13/ ? - do any of the following files exist on your machine? And if so what is their content? /etc/gre.conf /etc/gre64.conf /etc/gre.d/gre.conf /etc/gre.d/gre64.conf
(In reply to comment #3) > It's trying to use seamonkey-2.x, which is not a supported renderer. I'm not > sure why it's trying this though. Questions: > > - which linux distro/version are you using? > - is /usr/lib/seamonkey/ a link to /usr/lib/seamonkey-2.0.13/ ? > - do any of the following files exist on your machine? And if so what is their > content? > > /etc/gre.conf > /etc/gre64.conf > /etc/gre.d/gre.conf > /etc/gre.d/gre64.conf Hi, I am using Slackware 13.1 32 bits in a VMWare Virtual Machine. The same happens in Slackware 13.1 32 in a real machine. yes, /usr/lib/seamonkey/ a link to /usr/lib/seamonkey-2.0.13/ Non of the files (/etc/gre.conf /etc/gre64.conf /etc/gre.d/gre.conf /etc/gre.d/gre64.conf) exist in my distro.
That likely explains why seamonkey is being found anyways. You should be able to make the crash go away by setting Linux environment variable MOZILLA_FIVE_HOME=/dev/null before launching Eclipse. However you'll probably find that Browser functionality is not working (you can confirm this by trying Eclipse's Internal Web Browser view). It seems like your linux distro does not have a WebKitGTK or XULRunner available, because the Browser attempts both of these before falling back to trying something like seamonkey. Can you confirm that neither of these is present in /usr/lib/ ? And if not, the easiest way to get this working is to download XULRunner 1.9.2.x and install it ( https://developer.mozilla.org/en/XULRunner_1.9.2_Release_Notes ). Once you do this the Browser should auto-detect it and use it.
Hi, Yes, that was the problem. After installing XULRunner. All runs fine.\ Many thanks for the help. Carlos.
Fixed
No problem, glad to hear it's working for you now. As a side note I've logged bug 344270 for the crash you were originally seeing.
