Source lookup error when looking at avariable value in the debugger [message #235842] |
Tue, 12 September 2006 22:21 |
Eclipse User |
|
|
|
Originally posted by: james_adams.yahooo.com
When stepping through some code using the debugger I get the following
message in the field which displays under the variable name/value table
when I highlight a variable:
org.eclipse.core.runtime.CoreException: Source lookup error
This doesn't happen when I highlight "this" or a primitive type variable.
I get the same behavior after a restart of Eclipse.
Can anyone suggest a fix for this, or how I night prevent it from
happening in the future? This is not the first time this has happened to
me, and unfortunately I can't remember what sorted it out the last time.
Thanks in advance for any help with this problem.
--James
|
|
|
|
Re: Source lookup error when looking at avariable value in the debugger [message #236136 is a reply to message #235842] |
Wed, 20 September 2006 20:47 |
Eclipse User |
|
|
|
Originally posted by: james_adams.yahoo.com
In an attempt to get around this error I first scrapped my .metadata, and
when that had no effect I then reinstalled Eclipse 3.2. Still the problem
persists. At this point I'm assuming that there must be something amiss
with my Java installation, although I am using the latest Java JDK/JRE.
Can anyone suggest a next step I should try? This is a very handy feature
of the debugger that has been disabled, and I'd *really* like to restore
it.
Thanks in advance.
--James
|
|
|
Re: Source lookup error when looking at avariable value in the debugger [message #237637 is a reply to message #235842] |
Wed, 25 October 2006 17:00 |
Eclipse User |
|
|
|
Originally posted by: james_adams.yahoo.com
I think I have figured out what is happening. Some libraries in my build
path have source attachments. If these files aren't found I get the
source lookup error. Once I remove the source attachment or edit it so
that it points to the right source directory or source JAR then the
problem disappears. The solution I think is to have the source attachment
directory or JARs included as a folder in the project, so the source can
be found in the project, rather than in some random directory on the local
machine (which may or may not be present on another machine). This is
what happened in my case -- another developer made a source attachment to
a directory outside of the project on his local machine, and when I
checked out the project the build path (.classpath) specified a source
attachment location which wasn't present on my machine. So when I started
to debug I started to see the exception complaining that the source
attachment file or directory wasn't being found.
--James
|
|
|
|
Powered by
FUDForum. Page generated in 0.04267 seconds