eclipse indigo major bug - eclipse

I have been using Eclipse forever, but only today I upgraded to Indigo.
Using Eclipse Indigo on Mac 10.6 *
Files won't update after editing them and saving them. If I add blank lines and then save, then if I start debugging, the debugger will go through the lines that were there before, but now those lines are empty and the actual lines that the debugger is executing are a couple of lines below (due to the added blank lines). Debugger executes blank lines??!! Same thing if I change the code. If the file says X=5, and I change X=6, then debug, X will still be 5 ????!!!! Am I missing some editor caching option or smth ????
Things I have tried:
1. clean all projects, rebuild all projects
2. Delete projects, re-add them
3. delete files, write them from scratch
4. all auto-build and auto-refresh options are on
5. tried to change the workspace, the bug presists
6. tried to play around with the -xms128M and -Xmx786M option in the .ini file
7. tried restarting Eclipse and restarting computer

The problem was some discrepancy between the java version of the VM and the project's "facet" version. (whatever that is).
The thing I dont get is why the project was still running if there were problems reported on the "Problems" view and no new .class file was even compiled. Why it was running an outdated .java file, when the code on the actual display was different? (thus the ghost effect).
Is there an option that allows the eclipse to run outdated .class files if no new .class file could be compiled cause of compile errors?

Related

Eclipse opening and then closing immediately

Eclipse keeps showing the splash screen and then closing immediately after...I just downloaded it so I haven't had the opportunity to make a work space. I've tried uninstalling and reinstalling, the file has already been unzipped at this point I have no idea as to what I should do about this.
Make sure that you have installed Java JDK properly
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
Whenever it (Eclipse) encounters a problem that does not warrant launching a dialog, Eclipse saves a report in the workspace log file. The log file can be looked at in four alternative ways.
Locate the file yourself, see workspace/.metadata/.log.
Start Eclipse using -consoleLog. This will print the messages
that normally go to the .log file in the enclosing shell/command window. When the Java VM suffers a hard crash, it produces a separate logging file named something like hs_err_pidXXXXX.log. These files are also helpful for diagnosing
problems.
(Other two might not be useful in your case)
Window > Show View > PDE Runtime > Error Log. This gives you a view
with the contents of the .log file.
Help > About Eclipse Platform > Configuration Details. This
prints out a great number of details about the environment and
also concatenates the .log file. Great for including in a bug
report.
Source
Make sure that Java installed properly..
Uninstall Java and install again, this worked for me

Eclipse User Interface glitch

So I wanted to start learning Eclipse but ran into a strange error. I have tried re-installing Eclipse multiple times and changing the theme but to no avail. The UI ends up always looking like this:
EDIT: I figured out a solution. Instead of deleting the eclipse exe on my computer and downloading a new one, I searched for files and programs on my computer with the keyword "eclipse" and literally deleted them all (except for files noted "important system files"). After deleting 1,500 files, I redownloaded the latest version and have no problems....yet

Eclipse crashed and deleted all my work

Eclipse crashed and deleted all project files, including written by me and XML files from another program which were not related to Eclipse.
Is it possible to force Eclipse or JVM to use trash can, so that if it goes mad and delete everything, files could restored.
UPDATE
Files were definitely wiped out. This was checked with third party file managers. Also entire disc were searched for traces.
Some good news is that Eclipse history remained. This allowed to restore some files I changed from Eclipse. But this project was consisting of multiple other files, that were written not by me (taken from other libraries) or contained some data I was editing not in Eclipse (like XML or raw data).
All these files were wiped out by Eclipse.
If this would not happen to me I would also say it is unlikely. But it has happened.
The problem is somehow related with
(1) Eclipse
(2) Maven (m2e)
(3) Eclipse RCP
(4) Tycho
At some moment Eclipse started to show numerous error windows and I was to kill the process. After that I found files absent.
So I need some extra protection layer.
UPDATE 2
Crash repeated. This is a message during file wiping out:
This time I was not using Maven and Tycho.
UPDATE 3
Third crash.
Crash occurs only after error Application ... could not be found in the registry, which itself buggie.
UPDATE 4
Still unable to reproduce situation from scratch...
UPDATE: I think from this question you were working on an Eclipse RCP plugin or something like that when this happened.
So you probably broke your Eclipse in some fashion. Do not trust anything Eclipse tells you at this point! Look at the actual filesystem!
Eclipse crashed and deleted all project files, including written by me and XML files from another program which were not related to Eclipse.
That's highly unlikely. (Especially if those XML files were not in the workspace. But even if they were, it's very unlikely.) You probably opened a new workspace without realising it, or maybe Eclipse has some bug where it won't show you files that are actually there. Or maybe you accidentally switched to the wrong view (in Java the normal view for files is Package Explorer, if I remember correctly).
Or maybe you were storing your workspace on a USB stick (aka pen drive) or network drive and you accidentally disconnected from it without realising it.
Check in the workspace (the actual workspace you were using at the time, not the workspace you are now using, which, as I said, might not be the same thing), using Windows Explorer (if you are using Windows) or Finder (if you are using a Mac) or using ls (if you are using something else). Are the files really gone?
This Was My Fault
I was setting up a workspace location pointing to project folder and also setting clear workspace checkbox.
::shame::

Eclipse Crash "java was started but returned exit code = -805306369"

I'm aware there is an identical post here but none of the proposed solutions have changed anything and they are quite old (problems to do with Java6) and seem to be referring to a bug to do with Eclipse.
My problem is when I am developing in Eclipse for RCP and RAP Developers; either making changes to java files or changing dependencies etc, Eclipse randomly hangs and then freezes. I have to force close eclipse and I get this message
Things I have tried so far:
Restarted eclipse and PC
Added the -clean command to the very beginning of the eclipse.ini file
Created a brand new work space and attempted to develop in that
I'm running on the latest version of Java (1.7.0_13) and haven't got a clue what to do next.
The problem has happened 4 or 5 times in a number of different occasions:
When I have tried to add a new package to the src folder
When I have tried to add a class to a package in the src folder
When I have tried to edit a class in a package in the src folder
When using Ctrl+Space in a class in the src folder
Any advice/tips would be greatly appreciated! Need to get this problem sorted so I can get developing for my 3rd Year University Project :)
java was started but returned exit code = -805306369
is caused by Eclipse´s corrupted workspace, I solved my problem with these 3 steps:
1) Go to your workspace and rename it.
2) Start your eclipse and by default it will create a workspace.
3) Go to File -> Switch Workspace, choose your original workspace.
After a lot of researching and filing bug reports to no avail I tried one last clear out of Java and fresh installs of Eclipse to try and fix the error and it seems to have worked.
Here is what I did:
Un-installed Eclipse for RCP and RAP developers
Un-installed Java from my PC and deleted any old Java folders that were left behind (I didn't do this in previous clear outs so maybe there was an old version of Java messing something up)
Did a fresh install of Eclipse for RCP and RAP developers and a fresh install of the latest Java
I also deleted my old PATH variable for Java in Environment Variables and put the new one at the front of all the other entries
This seems to have fixed the error for now so hopefully it won't be a short term fix
I opened another instance of eclipse and it prompted me to choose a new workspace. I did so and there it was resolved. Then I closed the new workspace and resorted back to old workspace as usual.
If using Maven projects, check pom.xml, this may corrupted. Mine resolved by fixing pom file.
java was started but returned exit code = -805306369 caused by Eclipse´s currupted workspace, I solved my problem with this 4 steps:
Close Eclipse.
Kill the adb from task manager.
Start Eclipse and by default it will create a workspace or start with new workspace.
Go to File -> Switch Workspace, choose your original workspace.

Eclipse CDT shows errors before project is built

I am having a minor problem with Eclipse CDT Juno.
When I open up Eclipse for the first time, it will show many C/C++ Problem errors which put red x's on all of my projects. Many of these errors are "no such file or directory" errors for #include'd header files. However, after I clean and rebuild my projects, all of the errors go away.
I have double checked all of my indexer settings, and the index paths are pointing to the right place. I also believe the indexer is setup correctly because after a build, all of the "no such file or directory" errors are gone, and I can navigate through the source code without any red x's.
I have also tried Index->Rebuild and Index->Freshen All Files, but the only thing that will clear the errors is a clean/build.
I feel that I shouldn't have to rebuild all of my projects every time I open Eclipse. Any thoughts???
I was finally able to fix this by deleting the .metadata folder and rebuilding the workspace from scratch. What a pain, but at least my projects load without errors when I launch Eclipse.