| RE: [eclipse-dev] HELP! Eclipse won't re-start after crash |
> First of all, when you say "most recent stable", do you mean the 4/16 M5 build?
Sorry. Yes, that's it.
> Next question ... were you able to capture any information after the crash (content of >.metadata/.log, anything on the console).
this entry is repeated over and over. I can't seem to find the location of the mru list or I would delete it.
<log-entry date="Thu May 09 13:44:28 EDT 2002">
<status
plugin-id="org.eclipse.core.resources"
severity="INFO"
message="Unable to restore mru list - cannot instantiate input element: org.eclipse.ui.part.FileEditorInputFactory"
code="4">
</status>
</log-entry>
Thanks,
Scott
-----Original Message-----
From: klicnik@xxxxxxxxxx [mailto:klicnik@xxxxxxxxxx]
Sent: Thursday, May 09, 2002 1:52 PM
To: eclipse-dev@xxxxxxxxxxx
Subject: Re: [eclipse-dev] HELP! Eclipse won't re-start after crash
Scott, we'll need a bit more information to go on.
First of all, when you say "most recent stable", do you mean the 4/16 M5 build?
Next question ... were you able to capture any information after the crash (content of .metadata/.log, anything on the console).
In the M5 build there is a file install/platform.cfg. If you hit this problem again, try deleting it and restart ... see if it helps.
Without having more to go on it is hard to say what is causing this. I would suggest that if this happens again, open a defect in bugzilla, attaching .metadata/.log and install/platform.cfg to the defect, and describe what you were doing when you crashed. Open it againsts "platfrom" project, "update" component and we'll try to diagnose it from there.
"Weaver, Scott" <Sweaver@xxxxxxxxx>
Sent by: eclipse-dev-admin@xxxxxxxxxxx
05/09/2002 12:49 PM
Please respond to eclipse-dev
To: "'eclipse-dev@xxxxxxxxxxx'" <eclipse-dev@xxxxxxxxxxx>
cc:
Subject: [eclipse-dev] HELP! Eclipse won't re-start after crash
version: most recent STABLE release.
OS: Win2k
When eclipse crashes, it will not restart and requires a re-install and re-creation of all of the projects. This has happened to multiple developers in our office multiple times. Is there anyway to fix this without a complete scratch reload???
Thanks,
Scott