IDL crashes during the use of Common Variables

Prev Go to previous topic

Go to next topic

Last Post 06 Dec 2013 05:18 AM by anon

4 Replies

Sort:


You are not authorized to post a reply.

Author

Messages

anon

New Member

Posts:

06 Dec 2013 05:18 AM
Hi, I'm using IDL 8.2.3 on a Windows 7 64 bit machine. I´m getting in to trouble when I use common variables in connection with the function lsode. I do not have the problem running the same code with the same idl version on a linux machine. Has anybody an idea on this? Edit: Java runtime environment is up to date. The header of the error log is: # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fed7b96404, pid=8724, tid=2772 # # JRE version: 6.0_17-b04 # Java VM: Java HotSpot(TM) 64-Bit Server VM (14.3-b01 mixed mode windows-amd64 ) # Problematic frame: # C [idl.dll+0x4b6404] # # 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. # Thanks, Heiner

Deleted User

New Member

Posts:

06 Dec 2013 10:48 AM
Hi Heiner, Please, try renaming (or even deleting) the following hidden directory, under your home folder: .idl Just simply rename it to _idl. After doing that, re-start IDL. That hidden folder will be re-created. Does that help? Let us know. Thanks. Fernando

Deleted User

New Member

Posts:

09 Dec 2013 07:34 AM
Hi Fernando, I found the file and renamed it. IDL crashes no more, but do not find other subroutines I call in the code. When I add the subroutine folder to the IDL paths, IDL crashes again. :( Thanks and regards, Heiner

Deleted User

New Member

Posts:

16 Dec 2013 11:01 AM
Have you tried running your code from command-line IDL? If not, I think you should give this a try. To launch command-line IDL, go to Start > "All Programs" > IDL 8.2 (or ENVI 5.0) > Tools > "IDL Command Line". If running the program from command-line helps, you can try using the "-outofprocess" switch when launching the IDL workbench and see if that helps with the problem. To do this, right click on the shortcut you use to open IDL and then select "Properties". Then, change the "Target" field to say the following: "C:\Program Files\Exelis\IDL83\bin\bin.x86_64\idlde.exe" -outofprocess

Deleted User

New Member

Posts:

05 Jan 2014 03:58 AM
Hi Dave, thanks for the hint. I tried the IDL console and IDL crashes. Afterwards I tried the 32bit Version and it worked. The 32bit idlde Version worked as well. Seems it has something to do with 32/64 bit ;) Using the 32 bit IDL is a good workaround for me. Thanks, Heiner

You are not authorized to post a reply.