当进入类实例化时,eclipse调试器转到本机代码 [英] When stepping into class instantiation, eclipse debugger goes to native code

查看:110
本文介绍了当进入类实例化时,eclipse调试器转到本机代码的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近升级到helios,现在每次进入一个类的构造函数(例如 Cat myCat = new Cat(); )时,eclipse调试器显示堆栈作为



: p>

要获取实际的构造函数代码,我必须多次出来,这很烦人。每个类都会发生这种情况,尽管堆栈中我从来没有在控制台中看到任何错误信息。我如何解决这个问题,直接进入我的类的构造函数?



这只会在第一次使用类时发生,甚至是在相同的src文件与当前的一样。

解决方案

Eclipse在Java调试器首选项中有一个步骤过滤器首选项。它的默认首选项过滤掉 java.lang.ClassLoader ,但是这不工作。这可能与最近安装并切换到使用jre7有关。为了解决我的问题,我添加了一个过滤器来遍历 java.lang 包中的任何代码。




I recently upgraded to helios and now every time I step into a constructor for a class (e.g. Cat myCat = new Cat();), eclipse debugger shows the stack as

:

To get to the actual constructor code, I have to step out several times which is annoying. This is happening with every class and despite the stack I never see any error messages in the console. How do I fix this so it directly steps into the constructor for my class?

This only happens the first time the class is used, and even for classes that are in the same src file as the current one.

解决方案

Eclipse has a step filter preference in the Java debugger preferences. Its default preference filters out java.lang.ClassLoader, however this wasn't working. This might have something to do with recently having installed and switched to using jre7. To solve my problem I added a filter to step through any code in the java.lang package.

这篇关于当进入类实例化时,eclipse调试器转到本机代码的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆