An error has occured. Please see log file - eclipse - eclipse

When I start up Eclipse, it gives me an error saying:
An error has occurred. See the log file
/home/Vendetta/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1428564435095.log
on Linux Debian
Can you tell me what I should do?

Well whenever I've run into similar problems, it usually meant that a plug in had become out of synch with my eclipse file directory.
Unfortunately I can't give you much more than a generic "make sure your workspace is safe and re-download eclipse" with the information you've given.

Related

Error in NS2 debugging using Eclipse: "Cant find a source file at... "

I am trying to debug NS-2.34 using Eclipse Luna 4.4.2 under Ubuntu 13.10, and I had successfully configured NS2 and Eclipse for debugging by following the instructions from here "https://erl1.wordpress.com/2012/01/11/using-ns-2-with-eclipse/." The problem is, when I start debugging, debugging will not continue due to the error
Can't find a source file at "/build/buildd/eglibc-2/17/elf/dl-debug.c"
Locate the file or edit the source lookup path to include its location
I tried to locate the file in my system but I can't seem to figure that part out. How can I solve this error?
I think that's one of the many reasons why a lot of people transfer from NS2 to NS3 when they find that the module they would like to use is available in NS3.
For your problem, the page you are referring to has been a long time ago and there might be conflicts caused by new version.
For me, as a ns2er, when I modified some code or add new files, I just do "make" command and see what I got in the terminal. It works in most of the time.
Cheers,
Zeyu

Why does eclipse close by itself while running?

It's been happening lately for some unknown reason.I have the latest version of Eclipse ADT (25 Sept 2014) and it just shuts off while I'm working. Any ideas?
Start Eclipse from a terminal to see the standard output. Chances are that the Java VM runs into a problem because of SWT which can crash the VM. Note: If you're using Windows, you may have to use java.exe instead of javaw.exe to get output.
Also look into the Error Log. Eclipse has a view for that or look into the file .../workspace/.metadata/.log The file might contain an error message.
If you find an error in either the console or the error log, let us know and we might be able to help.
The issue could also be because of the JVM that was chosen for the project.

Error opening Eclipse

I am unable to open Eclipse IDE. The error displayed is as below
Any idea what could be the reason? And how do I solve this??
Note: I ran CCleaner recently (any registry issue??) and I got error executing my open Eclispe project. On restarting I get this issue. Is re-installation going to help? Am going to do that and update result here. And I would really like to know what caused this for future precautions.
Update: Same error for new installation. But this time got error regarding lauching JVM and missing dlls so going to reinstall Java.
Unable to understand what might be the exact problem , still giving it a shot.
Did you go through this URL http://michaelzanussi.com/?p=468
Appears to be the same issue , resetting JAVA_HOME and PATH solved the issue for him
The authors of Eclipse strongly recommend manually updating the Eclipse.ini file to point directly to the JRE that you want to use rather than relying on Windows environment variables.
Also C:\Windows\System32 is a really strange place to find the Java Runtime Environment files, typically they wind up in C:\Program Files\Java or C:\Program Files (x86)\Java.

Codecover plugin and eclipse - fatal error

I installed CodeCover to my STS so I can use it in my project. I can run code cover and get the measurments, but there is one thing that is bothering me.
If I enable code cover for a given project, everytime when I make a change to a source file and then save it I get this error message:
[FATAL]An error occured when trying to compile instrumented sources
if there are some errors reported by eclipse validator in some project file. Can I disable this feature, because it is really frustrating that I save one file and I get bit message that there are errors, even if I can see them underlined red by the editor.
This is most likely a bug, I suggest you file a bug at the project web-site, or try to fix it yourself by getting the source.

Why do I get this error in Eclipse - can it be that Java runtime version is incompatible?

In Eclipse(version 3.6.2.M201102101200/Helios service release 2). I am getting a strange error when I run a large Java project called ACE toolkit. Below is a picture:
What are possible reasons it would do this?
can it be that Java runtime version is incompatible? The project was built for Java 1.5, but I have 1.6 running.
I appreciate any tips or advice.
There could be any number of reasons for eclipse crashing, from insufficient memory to a misbehaving plugin. The first place to start troubleshooting would be the C:\path\to\your\workspace\.metadata\.log file. You might find something helpful if you examine the end of this file soon after eclipse crashes.
From the documentation:
Eclipse has a log file where problems are recorded and usually this is the first thing that an Eclipse developer asks for when you report a problem. The log file can be found in a couple of places:
Workspace log - This is the most common location for the log file, It is stored in your workspace in the meta-data directory. Check out
workspace/.metadata/.log.
Configuration log - Sometimes information is recored in the configuration log file instead of the workspace log. (especially if
the workspace hasn't been created yet, there isn't one, or it cannot
be created) Check your configuration area for a configuration log
file. (configuration/.log)
Startup - Occasionally problems happen in the system really early before there is a workspace and before there is a configuration area.
This means that there is nowhere to write the log file so information
is written to the console, See the notes below on running with a
console to get these messages.