Community
Participate
Working Groups
Whenever I connect with the debugger to my application server (oc4j on jdk1.4.2_05), stop on a breakpoint and inspect a variable via Ctrl+Shift+I a message box pops up: "JDI thread evaluations (Error: Exception processing async thread queue)". After that with every step I take through the code the same message pops up again which makes further debugging impossible and requires to restart eclipse. Since I just switched from version 3.1 to 3.2 I can state that this behaviour is new, I never had it before. Here's the exception from the logfile: !ENTRY org.eclipse.jdt.debug 4 120 2006-08-22 09:23:30.718 !MESSAGE Exception processing async thread queue !SUBENTRY 1 org.eclipse.jdt.debug 4 120 2006-08-22 09:23:30.718 !MESSAGE Exception processing async thread queue !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructionCompiler.containsALocalType(ASTInstructionCompiler.java:376) at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructionCompiler.visit(ASTInstructionCompiler.java:2651) at org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:236) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2466) at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2513) at org.eclipse.jdt.core.dom.ReturnStatement.accept0(ReturnStatement.java:135) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2466) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2536) at org.eclipse.jdt.core.dom.Block.accept0(Block.java:135) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2466) at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2513) at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:501) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2466) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2536) at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:483) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2466) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2536) at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:212) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2466) at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.createExpressionFromAST(ASTEvaluationEngine.java:389) at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.getCompiledExpression(ASTEvaluationEngine.java:204) at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.evaluate(ASTEvaluationEngine.java:89) at org.eclipse.jdt.internal.debug.ui.JavaWatchExpressionDelegate$EvaluationRunnable.run(JavaWatchExpressionDelegate.java:144) at org.eclipse.jdt.internal.debug.core.model.JDIThread$ThreadJob.run(JDIThread.java:2467) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
I filed this bug after having searched Google and this bug database without finding anything which matched. Today I realized that I ought to have checked the official eclipse newsgroup and there I found something about it. The source of the problem is an expression in the expression view which was left there and which couldn't be evaluated at that point. But nevertheless I think eclipse shouldn't give me a messagebox with every step I take in the debugger and without giving me more details in that message.
Fixed in 3.2.1 *** This bug has been marked as a duplicate of 119860 ***
