Hi - running the Eclipse SDK on the latest MacOSX High Sierra I get a 'segmentation fault' on startup which is perfectly repeatable, see screenshot. How can I run the SDK on my Mac?
Please could you try to download eclipse from this link and try running it? Let me know if you have the same error on startup.
Yes, that fails with the same message.
Ok, so it seems a problem with the Eclipse distribution, not an error caused but any additional plugin added by Justinmind.
Do you mind to try with the non 64-bit distribution?
All the links to the 32bit 3.8.2 SDK are broken, tried a few of them. So if I used a more recent version of Eclipse SDK can I then add the Justinmind plugin?
Version 3.8.2 dates back to January 2013 - surely you support a more modern version of Eclipse?
I'm not sure, but probably there are some plugin dependencies incompatibilities with modern versions of Eclipse. Our software is based on the previous Eclipse 3.X version, Eclipse 4 made huge changes and dependencies could be very different.
I will need to try it by myself to be sure, maybe these problems don't exists in order to develop a custom plugin.
I'm going to do some tests and I'll reply you back once I have some results.
I verified that Eclipse 4 will generate incompatibilities between different plugin versions .
I did some research on your original problem starting our SDK and I found some users having similar problems with eclipse.
Seems that extracting the .zip contents using "The Unarchiver" application (or maybe another similar tool) could cause this error. Please could you unzip it using the command line as suggested on the eclipse forum?
Yeah this was very odd - if I use Finder to simply explode the .dmg then it fails to load with the access violation, but if I use Path Finder file manager then it runs as expected. So I've got a fix - thanks for the help and the excellent debugging !
The SDK was updated for version 8.4 and this issue should be now fixed.
It seems that the bug/fault is back in 10.13.6.
I tried the zip fix, using my terminal rather than going through the finder. But that didnt do much for the problem.
I get the same segmentation fault as Colin
Replies have been locked on this page!