I'm trying to start eclipse but it crashes after the splash screen and before workspace selection.
This is version: eclipse-java-indigo-SR2-macosx-cocoa-x86_64 on Mac OSX 10.6.8
Launching the eclipse application or executing the alias from a shell ./eclipse (or Eclipse.app/Contents/MacOS/eclipse) results in a segfault.
$ ./eclipse
Invalid memory access of location 0x10 rip=0x7fff84ea3164
Segmentation fault
However, it runs successfully as the super user
$ sudo ./eclipse
Password:
This is fine for now, but running eclipse under sudo does not seem like a good idea.
To make this stranger still, this installation of eclipse worked fine a few months ago and I can't remember changing anything relevant.
Any ideas?
Thanks
Before taking the more drastic step of re-installing Java on Mac OS X [not always so simple :( .. ], I just reinstalled Eclipse and ADT - and it worked fine after that.
In my case, I got this error trying to start Eclipse
Segmentation fault: 11
.. it appeared in my Eclipse ADT setup after I updated the Android SDK for Google Play Services, and then tried to run Installation of update from "Check For Updates". Restarting the computer did not help.
I would try re-installing Java. The Apple installer might thwart you, but this can help get past it.
I'd suggest getting the Java Developer package from Apple, as it includes Javadoc and source for the core libraries.
Related
I have installed eclipse aarch64 based on my mac m1.
it was working fine. later i stopped using it for few days but i was just opening and closing it just to make sure it is not crashing as it used to happen with x64 version.
Now even with aarch it is crashing.
As soon as i open it via launch pad it says 'The apllication 'Eclipse'can't be opened.
Here are the details of eclipse and jdk version that i am currently using.
Eclipse: eclipse-java-2021-12-R-macosx-cocoa-aarch64
Jdk: jdk-17_macos-aarch64_bin
I've just had the same problem on the second launch of Eclipse from a fresh installation. The solution was to re-sign the app with an ad-hoc signature:
sudo codesign --force --deep --sign - /Applications/Eclipse.app
I started developing in Codename One a few days ago, using IntelliJ, but since it was causing some problems, I decided to try it with Eclipse.
I got a fresh install of Eclipse Proton for Java developers on my Mac Pro running OS Sierra 10.12.6 and I can't install the Codename One plugin.
I can find it in the marketplace, but when I try to install it starts the process but soon stops and pops this message. After I press ok, I can select features to install as seen here. After I press Confirm it does nothing, and presents this. I have already installed other plugins successfully, this is the only one giving me troubles.
I tried accessing that link but it leads to a standard 404 error page on codenameone's website.
I can't seem to find a way around this, as even trying to install the plugin through Eclipse marketplace website leads to this error.
Any help is appreciated :)
I wanted to start PHP development and installed Apache, php 7.1 and xdebug with homebrew on my mac with OSX Sierra. Often (but not always), when I go to debug mode in Eclipse and step through my code, Eclipse stops working and crashes hard (program doesn't respond anymore).
Now I absolutely have no clue where I could start to analyze the error. Maybe it's an issue with Eclipse and XDebug?
Any idea where where to start and where I could find some helpful information (logs etc.)?
I'm attempting to run an iPhone app in the Trigger Toolkit, but I keep getting "Unable to locate GDB" in the console, several seconds after "Connecting to remote debug server" . I've updated xcode, installed gdb separately through homebrew, and am able to run it (gdb) through the command line.
Thanks in advance for any relevant advice!
I'm guessing you're using a pre-v2.0.1 platform version here, and that you've updated to Xcode 5?
I was able to reproduce this error in that configuration. Xcode 5 doesn't support GDB, which we were previously using to communicate with the app running on your device.
If updating to use newer platform versions isn't an option for you, you could use an older installation of Xcode (you can have several versions installed as siblings), and use xcode-select to point us at it, e.g.:
sudo xcode-select --switch /Applications/Xcode4.6/Xcode.app
Yesterday I decided to start developing Android in my mac (Snow Leopard 10.6.8) 32-bit.
Everything was ok, i also imported my workspace which i worked in Linux for months. I open a project and compiles perfectly.
When i try to run the project it gives me this error :
"...android/sdk/tools/emulator64-arm : BAD CPU Type in executable"
I am using eclipse juno for mobile developers and downloaded the latest android sdk for mac
It looks like a 32-bit 64-bit issue. But i couldnt solve it yet.
Anyone had the same issue ?
I already found the problem.
Under the directory, android-sdk/tools/, i deleted every executable related to 64-bit system. Those files are :
emulator64-arm , emulator64-x86 etc.
Then relaunch the project and now it is working like a charm.
Hopefully this helps to anyone who suffers from the same issue.