2

I can't figure out how to step into "JDK" classes when I'm debugging remotely with Eclipse Kepler.

I have no problems stepping into "JDK" classes (like java.lang.Runtime) provided that I'm debugging a Java application launched by Eclipse (I'll call this "local"). However, when I attempt to debug the same application (launched with an InstallAnywhere LaunchAnywhere launcher) as a Remote Java Application on localhost, I can't step into JDK classes (I'll call this "remote").

In both cases (local and remote), I can step into my classes. But when I get to a method call in a JDK class while debugging remotely, Eclipse treats Step Into as Step Over. I'm using the same JDK for the local and remote debug session.

Is this an inherent limitation of remote debugging, or am I missing a configuration setting?

Improve this question

3 Answers 3

Reset to default
4

Check the following:

  • ensure that the Source Lookup Path contains the rt.jar using Edit Source Lookup dialog during the debug session.
  • the line number attributes are included the compiled classes which you are remote debugging, check this if you compiled them with eclipse.
  • ensure that the remote application which you are debugging uses a JDK instead of a JRE, since JREs doesn't include debugging information
Improve this answer
Sign up to request clarification or add additional context in comments.

7 Comments

While I did try that, it didn't work, and I don't think it's necessary. In a properly configured JDK (Window > Preferences > Java > Installed JREs > Edit..), src.zip will be configured as a Source attachment for rt.jar. Regarding line numbers, that's not it because I can still step through and use breakpoints for my code.
@David the "remote" application is launched by the mentioned launcher, that might be using a JRE, which has no debug info
Katona, that was the problem -- when I modified the LAX file to tell the LaunchAnywhere launcher to use the same JRE that Eclipse was using to debug it, it worked. If you edit your answer (or add a new one), I'll upvote and accept it. Thanks!
@David I included this in my answer, and kept the other suggestions as well
@David: I edited the third point. I still think the problem is that JRE doesn't contain the necessary information for debugging. See this answer how to check for the difference between the classes.
|
0

You will find the src.zip inside the JDK folder please add it to the debug configuration as an external archive in the source tab

Improve this answer

Comments

-1

window->preference->java->install->click add->standard VM->next: JRE HOWM :JDK PATH(NOT JRE PATH!)

if no source in rt.jar you should on rt.jar source Attachment to configure the source path. that's all

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.