|Trouble mapping object file to source file [message #985606]
||Thu, 15 November 2012 14:32
| Jim Anderson
Registered: October 2014
When I run 'about Eclipse SDK' from the menu, I get:|
Build id: M20100211-1343
My platform is CrunchBang Linux:
Distributor ID: Debian
Description: Debian GNU/Linux 6.0 (squeeze)
If I run 'uname -a', the release is:
I have been running Eclipse for a few years with the configuration I have been using. The major change in my work in the past week is that I'm now working, and debugging, more with source code in multiple jars.
The set up I use is to link Eclipse source code back to the source code in my development directory, which is outside the Eclipse working directory. When I work in Eclipse, it is finding and displaying the correct source code - no problem here.
When I try to debug, my program starts up fine, and I can step through the source code that is in the directory that contains the 'main' method with no trouble. However, when I reach code that is in class 'Pot' and I try to step into the code, Eclipse pops up a new window 'Pot.class', in a new tab, that tells me that 'The source attachment does not contain the source for the file Pot.class'. (I have attached a snapshot of that window).
When I select the 'Change Attached Source' button, a navigation window pops up and I navigate to the directory containing the source for Pot.java and select it. After I hit the 'OK' button, Eclipse reverts back to the former context and continues to prompt me to 'Change Attached Source'.
The bottom line is that I can not step through source code that is the auxiliary jar file.
BTW, I tried rebuilding the project after I ran into this problem, but the same behavior continues. After rebuilding, I looked into the work directory and by looking at time stamps, I concluded that the jar files in the eclipse work directory are getting built from the source files in my development directory.
Does anyone have any suggestions for me to try? Thank you in advance.
Powered by FUDForum
. Page generated in 2.97251 seconds