JDI 线程评估遇到问题
我正在运行 Java 版 Eclipse。我创建了 XML 文件的 DOM 版本。现在我想更改文件中元素的属性。我调用了一个方法，该方法调用了控制 DOM 的类中的方法，并且在调试时出现一个对话框，显示“JDI 线程评估遇到问题。异常处理异步线程队列”。
我是 Java 的新手，还没有遇到过这样的错误，我不知道是什么原因造成的。
如果有人对问题的原因和/或解决方法有任何建议......
非常感谢！
I'm running Eclipse for Java. I created a DOM version of an XML file. Now I want to change an attribute of an element in the file. I called a method that called a method in the class that controls the DOM, and I got a dialog box saying "JDI Thread Evaluations has encountered a problem. Exception processing async thread queue" while debugging.
I'm a relative newbie at Java and have not come across such an error, and I have no idea what's causing it.
If anyone has any suggestions as to the cause of the problem and/or ways to fix it ...
Thanks so much!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
请留意您的“观看”表达式 - 如果您不需要它们，请将它们全部删除。有时某些手表表达式会导致我出现此错误消息。
这也可以解释为什么人们会间歇性地发生这种情况（有时他们的手表分配会导致错误，但是重新启动或删除正确的手表可以在他们不知情的情况下解决问题。）
Keep an eye on your "Watch" expressions - if you don't need them, remove them all. Sometimes certain watch expressions have caused this error message for me.
This might also explain why it happens to intermittently for people (sometimes they have watch assignments that cause the error, however restarting or removing the right watch can solve the issue without them knowing it.)
Java 调试接口 (JDI) 是 Java 的一部分平台调试器架构。当对象的 toString() 方法不小心返回 null 时，就会出现触发此异常的一种明显方式。您可能想尝试不同的调试器，并且验证您的 XML 不会有什么坏处。正如评论中指出的，该问题可能会间歇性出现，表明存在线程同步问题。
The Java Debug Interface (JDI) is part of the Java Platform Debugger Architecture. One apparent way to trigger this exception occurs when an object's
toString()method carelessly returnsnull. You might want to try a different debugger, and it wouldn't hurt to validate your XML. As noted in comments, the problem may appear intermittently, suggesting a thread synchronization problem.调试时，此错误会悄悄出现几次。
您可以通过删除所有监视语句和所有断点并重新启动 Eclipse 来清理此问题。
This error occurs quiet a few times when you debugging.
You can clean this up by removing all watch statements and all breakpoints and restarting Eclipse.
如果源查找配置不正确，也可能会出现此问题。例如，假设有人想要观看表达式
foo.bar()。现在，如果源查找配置不正确，调试器将无法解析表达式foo的绑定（请参阅 这个 Eclipse 错误）。那么.bar()的调用将失败并出现 NullPointerException。The problem can also occur if source lookup is incorrectly configured. For example lets say one wants to watch the expression
foo.bar(). Now if source lookup is incorrectly configured, the debugger is unable to resolve the binding for expressionfoo(see this eclipse bug). Then the invocation of.bar()will fail with a NullPointerException.如果您为特定类配置了“详细信息格式化程序”（在 Eclipse 中：Java -> 调试 -> 详细信息格式化程序），则可能会出现此问题。尝试禁用它们。
This problem may occur if you have "Detail Formatters" configured for specific classes (in Eclipse: Java -> Debug -> Detail Formatters). Try to disable them.
当我调试表达式时，这在 Eclipse 中被复制：
""，它只是一个空表达式。因此，如果您遇到此问题，一种解决方案可能是检查您的某个表达式是否为空或相似，然后适当地将其删除。
This was replicated in eclipse when I was debugging the expression which reads:
"", which is just an empty expression.So, if you're getting this problem, one solution may be to check to see if one of your expressions is empty or similar, then aptly delete it.