Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » unable to restore java source locator
unable to restore java source locator [message #158988] Mon, 17 May 2004 06:43 Go to next message
Eclipse UserFriend
Hello,

I'm developing a java RCP application (stand-alone eclipse plugin) based on
Eclipse V3.0 M7
Everything has been working nicely until now:

If I try to debug my project, I get the error-popup: "unable to restore java
source locator: invalid format"

I can't find any documentation explaining anything about the error. What can
can I do to locate the problem?


Greetings,


Bernd
Re: unable to restore java source locator [message #159084 is a reply to message #158988] Mon, 17 May 2004 11:02 Go to previous messageGo to next message
Eclipse UserFriend
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=62434

Darin

"Bernd Hofner" <bernd.hofner@gmx.net> wrote in message
news:c8a4k1$l92$1@eclipse.org...
> Hello,
>
> I'm developing a java RCP application (stand-alone eclipse plugin) based
on
> Eclipse V3.0 M7
> Everything has been working nicely until now:
>
> If I try to debug my project, I get the error-popup: "unable to restore
java
> source locator: invalid format"
>
> I can't find any documentation explaining anything about the error. What
can
> can I do to locate the problem?
>
>
> Greetings,
>
>
> Bernd
>
>
>
Re: unable to restore java source locator [message #159130 is a reply to message #159084] Mon, 17 May 2004 14:11 Go to previous message
Eclipse UserFriend
Ah, well, I see, or do I not?

I didn't change the Eclipse release. The problem occured from within one
eclipse session.
I've been running the app in debug mode. Then I changed something in the
code and had to terminate.
Afterwards I tried to debug again and had the problem that the source editor
didn't synchronize with the currently executed line.
So I terminated again, did some Refreshing and Rebuilding, which didn't
impress the problem in the slightest.
Than, for lack of anything better to do, I opend the debug configuration to
enter -Xvm256k into the Java VM parameter field,
hoping to startle the environment into working.
After that I started the debugger again and -surprise - was rewarded for my
efforts!
Unfortunatly the reward consisted of the stated error message "unable to
restore...".
The .log wasn't of particular help either, because it just stated the same.
Needless to say, that removing the VM argument from the
debug cfg didn't whisk away the problem...
Again in spite of any logical considerations I just created a new debug
configuration, using the same parameters as the tainted one,
and - voil
Previous Topic:assert-try-finally-debugger interaction, stops in finally, not at assert
Next Topic:Eclipse M8 Ant problem/question
Goto Forum:
  


Current Time: Thu Sep 18 17:25:30 EDT 2025

Powered by FUDForum. Page generated in 0.02278 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top