Bug 282548 - Using Breakpoints -> 'JDI thread evaluations' has encountered a problem
Summary: Using Breakpoints -> 'JDI thread evaluations' has encountered a problem
Status: CLOSED DUPLICATE of bug 277574
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-06 11:57 EDT by Lysathor CLA
Modified: 2010-07-15 10:17 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lysathor CLA 2009-07-06 11:57:11 EDT
Using Breakpoints creates a dialog:
'JDI thread evaluations' has encoutnered a problem
Exception processing async thread queue
  Exception processing async thread queue
  java.lang.NullPointerException

Dialog is created again when stepping to next code line.
Dialog is also created again when clicking in "debug" (call stack) on the current execution method.

Contens of error log se below. 

-- Configuration Details --
Product: Eclipse 1.2.0.20090619-0620 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.jdt 3.5.0.v20090527-2000-7r88FEeFJePyvYeA33DjZ_c1

 
 
 
 Error
Mon Jul 06 17:57:37 CEST 2009
Exception processing async thread queue

java.lang.NullPointerException
	at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructionCompiler.visit(ASTInstructionCompiler.java:3166)
	at org.eclipse.jdt.core.dom.QualifiedName.accept0(QualifiedName.java:167)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528)
	at org.eclipse.jdt.core.dom.ReturnStatement.accept0(ReturnStatement.java:136)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
	at org.eclipse.jdt.core.dom.Block.accept0(Block.java:136)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528)
	at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:502)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
	at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
	at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
	at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:219)
	at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
	at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.createExpressionFromAST(ASTEvaluationEngine.java:414)
	at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.getCompiledExpression(ASTEvaluationEngine.java:233)
	at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.evaluate(ASTEvaluationEngine.java:115)
	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:2751)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comment 1 Darin Wright CLA 2009-07-08 09:32:13 EDT
The problem is being caused by a watch expression - can you tell us what sort of expression you have (had) in the Expressions view?
Comment 2 Lysathor CLA 2009-07-08 14:31:40 EDT
Sorry, cannot remember the watch expressions. But I am quite sure it was nothing complex, just showing local or member variables.
Comment 3 Darin Wright CLA 2010-07-15 10:17:29 EDT
This will be fixed with bug 277574

*** This bug has been marked as a duplicate of bug 277574 ***