comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » IDLDE crashes when opening menus
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
IDLDE crashes when opening menus [message #79499] Thu, 01 March 2012 10:26 Go to previous message
Christian is currently offline  Christian
Messages: 11
Registered: March 2012
Junior Member
This is a problem with the development environment - IDL itself seems
to be working fine.

I've got IDL 7.0 installed on Mac OSX 10.7.3 (this was a bit of a
hack, because the installer is a PowerPC app, and 10.7 doesn't have
Rosetta - in the end I just copied the entire folder from a
colleague's computer). Things have been working fine for a long
time. I recently took a break from coding to try and actually publish
some results, but now when I go back to IDL the development
environment crashes every single time I do something which generates a
pull-down menu (I *think* this is the common element). Certainly it
crashes if I click on the menubar, or right-click on a file/folder in
the project explorer - but otherwise IDL seems to be working fine
(including the little icon shortcuts below the menubar). I can
somewhat get work done because it's still possible to do many things
with keyboard shortcuts, but I can't update/commit from/to my svn
repositories which is certainly a big problem.

I suspect that at some point a java (?) update broke the eclipse hack
itt put together, but in that case I'm surprised that I haven't been
able to google any cases of other people with the same problem. Since
I wasn't actively coding as the time it's difficult to pin down what
broke it or even when - all I know is that in early January (?) it
worked and as of last week it doesn't.

Has anybody else had a similar problem?

I normally run it via a link to the "IDLSnapFileOpen" app in the main
directory, but the error message I get when the same problem after
running IDLDE from the command line is:
$ pwd
/Applications/itt/idl70/bin
$ ./idlde
Invalid memory access of location 0x0 eip=0x0
Bus error: 10


The "send your report to Apple" error log is 1179 lines long, so I
hesitate to post the entire message. The lines near the top I
(arbitrarily?) identified as important and have been googling for (and
hopefully brings some other people with a similar problem to this
page) are:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K]
---/--- SM=NUL /Applications/itt/*/idlde.darwin.universal.app/
Contents/MacOS/idlde
__TEXT 0000000000001000-0000000000004000 [ 12K]
r-x/rwx SM=COW /Applications/itt/*/idlde.darwin.universal.app/
Contents/MacOS/idlde

Application Specific Information:
objc[10162]: garbage collection is OFF

Java information:
Exception type: Bus Error (0xa) at pc=0000000000000000

Java VM: Java HotSpot(TM) Client VM (20.4-b02-402 mixed mode macosx-
x86)








Perhaps it is a red-herring, but I have attempted to learn more by
installing the non-itt version of eclipse (3.7.2)... this works,
although if I try the instructions here:
http://www.idlcoyote.com/workbench/addtoeclipse.html
For adding the IDLDE to this installation I can't get the hybrid to
work. On startup I get a "fatal error initializing DML" popup box,
followed by "fatal error initializing main IDL process" and the error:
Failed to load idl_jdml from /Applications/itt/idl70/idlde/
bin.darwin.i386 (it is set by the property JDMLDir.)
(although there is a file named "libidl_jdml.jnilib" there - perhaps
the naming convention changed between versions of eclipse?)

Incidentally, this is the same result that I get if I run the itt
idlde from the "wrong" directory:
$ pwd
/Applications/itt/idl70/idlde/idlde.darwin.universal.app/Con tents/
MacOS
$ ./idlde
Failed to load idl_jdml from /Applications/itt/idl70/idlde/
bin.darwin.i386 (Use default IDL)

So perhaps I should be running my hacked version of eclipse from a
different spot? Currently my script to setup things runs from the
first eclipse directory.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: strange behaviour of bytscl by large arrays
Next Topic: runtime application avoid multi open

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 18:35:35 PDT 2025

Total time taken to generate the page: 0.00411 seconds