| Re: IDLDE crashes when opening menus [message #79648 is a reply to message #79499] |
Wed, 14 March 2012 17:30   |
Christian
Messages: 11
Registered: March 2012
|
Junior Member |
|
|
So, I'm wondering how exact you mean when you say "the same"... if
there's some difference in our setups maybe some things can be ruled
out as lower probability. What version of IDL and OSX do you have?
I've also tried doing the modifications on both the latest version of
eclipse as well as 3.3, neither worked and both gave the same error.
Following this thread:
http://groups.google.com/group/comp.lang.idl-pvwave/browse_t hread/thread/e876ab4d48f64cd0
I tried to look at the dependencies of libidl_jdml.jnilib, but it
looks like they are all there:
$ otool -L libidl_jdml.jnilib libidl_jdml.jnilib:
libidl_jdml.jnilib (compatibility version 0.0.0, current version
0.0.0)
libidl_dml.dylib (compatibility version 0.0.0, current version 0.0.0)
libidl_bml.dylib (compatibility version 0.0.0, current version 0.0.0)
libidl_gmem.dylib (compatibility version 0.0.0, current version
0.0.0)
libidl.7.0.dylib (compatibility version 0.0.0, current version 0.0.0)
libidl_ops.7.0.dylib (compatibility version 0.0.0, current version
0.0.0)
libidl_ipcclient.7.0.dylib (compatibility version 0.0.0, current
version 0.0.0)
libMesaGLU6_2.dylib (compatibility version 0.0.0, current version
0.0.0)
libMesaGL6_2.dylib (compatibility version 0.0.0, current version
0.0.0)
libOSMesa6_2.dylib (compatibility version 0.0.0, current version
0.0.0)
libfreetype2_1_3.6.3.2.dylib (compatibility version 10.0.0, current
version 10.2.0)
libXm.3.dylib (compatibility version 4.0.0, current version 4.2.0)
/usr/X11R6/lib/libXp.6.dylib (compatibility version 6.2.0, current
version 6.2.0)
/usr/X11R6/lib/libXpm.4.dylib (compatibility version 4.11.0, current
version 4.11.0)
/usr/X11R6/lib/libXmu.6.dylib (compatibility version 6.2.0, current
version 6.2.0)
/usr/X11R6/lib/libXext.6.dylib (compatibility version 6.4.0, current
version 6.4.0)
/usr/X11R6/lib/libXt.6.dylib (compatibility version 6.0.0, current
version 6.0.0)
/usr/X11R6/lib/libSM.6.dylib (compatibility version 6.0.0, current
version 6.0.0)
/usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, current
version 6.2.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 88.1.5)
/System/Library/Frameworks/JavaVM.framework/Versions/A/JavaV M
(compatibility version 1.0.0, current version 84.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.4.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
Although I have to admit I'm not sure if I should be worried about all
these version 0.0.0 references...
On Mar 14, 4:13 pm, Christian <christian.veens...@gmail.com> wrote:
> So far, no resolution. I've just been using IDL without generating
> any popup menus and cursing whenever I accidentally do so and cause it
> to crash... I need to start doing some more serious coding today,
> though, so I won't be able to survive without interacting with my
> repository (the last thing I don't know how to do via a shortcut key).
>
> On Mar 14, 5:06 am, Anywhere <anyd...@gmail.com> wrote:
>
>
>
>
>
>
>
>> Hi,
>> i have the SAME EXACT error and I'm arrived in your exact same point.
>> i'm trying to search a way for resolve the fatal error of new eclipse
>> but for now no solution found.
>> Did you have resolved it in some way?
>
>> On 1 Mar, 19:26, Christian <christian.veens...@gmail.com> wrote:
>
>>> 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.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
