Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Hi there: I'm using IDL 7 in Fedora 9, but the GUI crashes when I run idlde. Is there anyone knows how to solve this problem? Here is the crash report: JVM terminated. Exit code=1 /usr/local/itt/idl/idl70/idlde/bin.linux.x86/jre/bin/java -Xms40M -Xmx256M -jar /usr/local/itt/idl/idl70/idlde/plugins/ org.eclipse.equinox.launcher_1.0.0.v20070606.jar -os linux -ws gtk -arch x86 -showsplash -launcher /usr/local/itt/idl/idl70/idlde/idlde.linux.x86 -name Idlde.linux.x86 --launcher.library /usr/local/itt/idl/idl70/idlde/plugins/ org.eclipse.equinox.launcher.gtk.linux.x86_1.0.0.v20070606/ eclipse_1020.so -startup /usr/local/itt/idl/idl70/idlde/plugins/ org.eclipse.equinox.launcher_1.0.0.v20070606.jar -exitdata 1e000f -vm /usr/local/itt/idl/idl70/idlde/bin.linux.x86/jre/bin/java -vmargs -Xms40M -Xmx256M -jar /usr/local/itt/idl/idl70/idlde/plugins/ org.eclipse.equinox.launcher_1.0.0.v20070606.jar
Could you remove the following 32bit package?: xulrunner-1.9-1.fc9.i386.rpm This should solve the problem. Are you using Firefox 3 beta version?. Greetings, fernando
On Jul 2, 9:57 am, santoro...@gmail.com wrote: > Could you remove the following 32bit package?: > > xulrunner-1.9-1.fc9.i386.rpm > > This should solve the problem. > > Are you using Firefox 3 beta version?. > > Greetings, > fernando This is a non-solution! Removing xulrunner removes Firefox 3 as well. I have the same problem, and am using the Firefox 3.0 release. There needs to be a better fix. This affects not only IDLDE, but also the help file menu as well. Thanks, Greg
Dear Greg, Are you using Fedora 9 64bit?. We had some other users with the same problems. Only one was using FC9 64bit and he fixed the problem by deleting that 32bit package. Firefox 3 64bit in his system continue to work fine. Other users using RH5 64bit has used the following method to fix their problem: 1- Download firefox-2.0.0.14.tar.gz (this is 32-bit) from http://download.mozilla.org/?product=firefox-2.0.0.14&os =linux&lang=en-US 2- Install it where you want. (For example: /usr/lib/ firefox-2.0.0.14) 3- Then, depending on your shell script, i.e. cshrc, .profile, or .bashrc file, set up the enviroment variable, like: export MOZILLA_FIVE_HOME /usr/lib/firefox-2.0.0.14 4- Now, try commands: idlde and idlhelp I asked a user of FC9 64bit to try that and it didn't work, that's why in that case the only solution was to remove the 32bit package that I mention in the previous reply. The HotSpot error message also points to libxul.so and that was the clue we have to solve the problem of the other users. Do you have such an error message too? Are you using a beta version of Firefox 3?. If Firefox is a 64bit application in your 64bit system then it shouldn't hurt to remove the xulrunner 32bit package. I understand that can be install again, but of course, this is a decision that you have to take, if you are confident working with Linux systems.
On Jul 3, 3:55 pm, santoro...@gmail.com wrote: > Dear Greg, > > Are you using Fedora 9 64bit?. > No - 32 bit. I have a 64 bit computer, but am currently running a 32 version of Fedora 9. > We had some other users with the same problems. Only one was using FC9 > 64bit and he fixed the problem by deleting that 32bit package. Firefox > 3 64bit in his system continue to work fine. > > Other users using RH5 64bit has used the following method to fix their > problem: > > 1- Download firefox-2.0.0.14.tar.gz (this is 32-bit) from > http://download.mozilla.org/?product=firefox-2.0.0.14&os =linux=e... > I actually thought of this and tried it, but it does not work. > 2- Install it where you want. (For example: /usr/lib/ > firefox-2.0.0.14) > > 3- Then, depending on your shell script, i.e. cshrc, .profile, > or .bashrc file, set up the enviroment variable, like: > > export MOZILLA_FIVE_HOME /usr/lib/firefox-2.0.0.14 > > 4- Now, try commands: idlde and idlhelp > > I asked a user of FC9 64bit to try that and it didn't work, that's why > in that case the only solution was to remove the 32bit package that I > mention in the previous reply. > > The HotSpot error message also points to libxul.so and that was the > clue we have to solve the problem of the other users. Do you have such > an error message too? > Yes. See below for the error message: > Are you using a beta version of Firefox 3?. If Firefox is a 64bit > application in your 64bit system then it shouldn't hurt to remove the > xulrunner 32bit package. I understand that can be install again, but > of course, this is a decision that you have to take, if you are > confident working with Linux systems. No -- I'm using the Firefox 3.0 release. For 32-bit, Firefox depends upon xulrunner, so I cannot simply remove it without removing Firefox. Installing or removing applications is a non-issue for me. Here is the error message: # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x04e862d4, pid=10449, tid=3087616320 # # Java VM: Java HotSpot(TM) Server VM (1.5.0_11-b03 mixed mode) # Problematic frame: # C [libxul.so+0x9ac2d4] # # An error report file with more information is saved as /tmp/ hs_err_pid10449.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # I was able to fix the idlde problem by adding the following line to / usr/local/rsi/idl70/idlde/idlde.linux.x86.ini -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null However, this fix *does not* work for idlhelp... ...so I'm still at a loss. Thanks, Greg
I have had similar troubles with IDL on fedora9. One machine is running in 64bit. Looking at strace it was mixing the 64bit and 32bit libraries. The fix was to rename the file /etc/gre.d/ gre64.conf to something else, then run idlde. Afterwards the file can be renamed to its original name and idlde keeps starting properly. Another machine is a new 64bit machine but it runs a 32bit os (the hard disk used to be in a 32bit machine that died recently and where idlde use to run). Now I get the same error message. This time I renamed the /usr/lib/xulrunner-1.9 directory to something else and ran idlde and it also started properly. After renaming the directory back to its original name, idlde still starts properly. In both case the help crashes (or when the xulrunner directory is renamed I get an error message on the console saying on the 32bit os Could not find compatible GRE between version 1.9 and 1.9. on the 64 bit os it actually works with the directory renamed ) I have a third machine, running 32 bit on a 32bit laptop and there idlde did not stop working but the help does not work In all cases I have an updated machine so xulrunner is version xulrunner-1.9-1.fc9 Cheers Christian
On Jul 4, 6:44 pm, Christian.Lup...@gmail.com wrote: > I have had similar troubles with IDL on fedora9. > One machine is running in 64bit. Looking at strace it was mixing the > 64bit and 32bit libraries. The fix was to rename the file /etc/gre.d/ > gre64.conf to something else, then run idlde. > Afterwards the file can be renamed to its original name and idlde > keeps starting properly. > > Another machine is a new 64bit machine but it runs a 32bit os (the > hard disk used to be in a 32bit machine that died recently and where > idlde use to run). Now I get the same error message. This time I > renamed the /usr/lib/xulrunner-1.9 directory to something else and ran > idlde and it also started properly. After renaming the directory back > to its original name, idlde still starts properly. > > In both case the help crashes (or when the xulrunner directory is > renamed I get an error message on the console saying on the 32bit os > Could not find compatible GRE between version 1.9 and 1.9. > on the 64 bit os it actually works with the directory renamed I have the EXACT same issue, any confirmed fixes? > > I have a third machine, running 32 bit on a 32bit laptop and there > idlde did not stop working but the help does not work > > In all cases I have an updated machine so xulrunner is version > xulrunner-1.9-1.fc9 > > Cheers > Christian
<jolleyspam@gmail.com> wrote in message news:89a18c55-4f37-439f-ad99-544d4fc8c3d2@z72g2000hsb.google groups.com... On Jul 4, 6:44 pm, Christian.Lup...@gmail.com wrote: > I have had similar troubles with IDL on fedora9. > One machine is running in 64bit. Looking at strace it was mixing the > 64bit and 32bit libraries. The fix was to rename the file /etc/gre.d/ > gre64.conf to something else, then run idlde. > Afterwards the file can be renamed to its original name and idlde > keeps starting properly. > > Another machine is a new 64bit machine but it runs a 32bit os (the > hard disk used to be in a 32bit machine that died recently and where > idlde use to run). Now I get the same error message. This time I > renamed the /usr/lib/xulrunner-1.9 directory to something else and ran > idlde and it also started properly. After renaming the directory back > to its original name, idlde still starts properly. > > In both case the help crashes (or when the xulrunner directory is > renamed I get an error message on the console saying on the 32bit os > Could not find compatible GRE between version 1.9 and 1.9. > on the 64 bit os it actually works with the directory renamed I have the EXACT same issue, any confirmed fixes? Not much to add here, but I also see this on all our 64 bit machines, and if someone comes across a confirmed fix let me know. I haven't seen anything at the IDL website yet. Cheers, bob
I am not quite sure how I got there but I have idl working and the help also working (by help I mean using the "Help Contents" menu option). No more crash. Updated the idl version to 7.0.3 (I think this prevents idlhelp command from crashing but it does nothing now: no crash, no errors, no results) Changed the Web browser preference (this also produced crashes before) - needed to disable xulrunner to prevent crashes by renaming temporarily /usr/lib/xulrunner-1.9 - New pref uses htmlviewer (or can be firefox directly) But I have one machine back to the default system browser and it seems ok so it might not be necessary Finally I applied the fix mentionned above (see Greg), i.e. editing idlde.linux.x86.ini to have -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null Cheers Christian P.S. On my 64 bit system I was unable to update to 7.0.3 until I disabled ipv6 (I used something like "ifconfig lo inet6 del ::1/128" on all my interfaces). Without this I was getting errors of "Network connection problems..."