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?
Check the following:
Source Lookup Path
contains the rt.jar
using Edit Source Lookup dialog during the debug session. 您会在JDK文件夹中找到src.zip,请在“源”选项卡中将其作为外部归档添加到调试配置中。
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
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.