Description of problem: When I start Eclipse I get an error box that says "'Initialize Indexing' has encountered a problem." If I click on the Details button I am told that "An internal error occurred during "Initialize Indexing"" and in the line below: java.lang.NullPointerException. Version-Release number of selected component (if applicable): eclipse-cdt.i686 1:6.0.2-4.fc13 How reproducible: Every time. Steps to Reproduce: 1. Start Eclipse 2. 3. Actual results: Error as described above. Expected results: No error. Additional info: Eclipse worked flawlessly on Fedora 12 on this same computer opening the very same project. This is still basically the same Eclipse version (Galileo) so am not sure why there is an issue now.
I should say that Eclipse still works after this exception. I have not yet found what the consequences of this exception are.
(In reply to comment #1) > I should say that Eclipse still works after this exception. I have not yet > found what the consequences of this exception are. Can you provide a traceback from the Error Log and attach it to this bug? Does indexing work on the C projects in your workspace? You can find out by opening a C file, high-lighting a C function and pressing F3. That should open the source file, if known, or the header file if we are talking about a C library function.
I did a few more tests. I downloaded the latest JRE from the Sun website, then changed the alternatives, and the problem is still there. That seems to indicate the problem is in Eclipse rather than Java. F3 appears to work. I selected a C function, pressed F3 and the header function where it was defined was open automatically. I closed all files and views, then closed Eclipse, reopened it, and there was no error. With it open the error message popped up the moment I opened a perspective (Project Explorer). If I have nothing open when Eclipse starts, and then open a file that belongs to the project I get an error, however if I open a HTML file outside the project there is no error. I don't know how to get the traceback you are talking about, as I know little about Eclipse, I can do it if you tell me how. However I am in Europe and is now past midnight, so it will be only tomorrow. Thanks for taking an interest in this.
Just notice two typos: 1. pressed F3 and the header *file* where it was defined was opened automatically. 2. the moment I opened a *view* (Project Explorer)
I found a workaround to my Eclipse issue: 1. Deleted ~/.eclipse 2. Deleted workspace 3. Created a new workspace 4. Created a new project in the new workspace 5. Copied source files from the backup of the old project to the new project. My workaround was suitable because my project is very small and makefile based, however might not suit people that have complex projects or heavy customization of Eclipse. Also note that just deleting ~/.eclipse was not enough. I am happy now, even though it took me a few hours to find a solution to this issue. You may close this bug if you want.
Hmm, I guess there was something wrong in the saved indexing information which the indexer was able to work around after displaying the exception occurred. Since you have deleted the old project and workspace, hopefully this was a one-time occurrence that has been fixed. I will close the bug as fixed in current release but if it happens again, please feel free to reopen. To see or get a traceback in the future, from the main window use the top menu item Window->Show View...->Other...->General->Error Log