Community
Participate
Working Groups
What steps will reproduce the problem? 1. In package view drag fields from one class to another 2. 3. -- Error Details -- Date: Thu Jul 01 08:13:57 CEST 2010 Message: Error in JDT Core during AST creation Severity: Error Product: Eclipse 1.3.0.20100617-0520 (org.eclipse.epp.package.java.product) Plugin: org.eclipse.jdt.ui Session Data: eclipse.buildId=I20100608-0911 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product Exception Stack Trace: java.lang.ArrayIndexOutOfBoundsException
Lysathor, please attach a full stack trace. The name of the exception is not sufficient information to debug this. Also, if possible when you are reporting bugs, please set the component correctly. You assigned this one to "APT", which is the annotation processing tooling; this bug has nothing to do with annotation processing. If you're not sure, a good first guess is either Core or UI.
*** Bug 318545 has been marked as a duplicate of this bug. ***
*** Bug 318546 has been marked as a duplicate of this bug. ***
Sorry for not providing sufficient or correct information. But that was what eclipse provided when I used the "report bug" feature of the error log. Usually that provies a full stack trace, but for this problem it did not. So please report that as a bug of that feature (is that Mylyn?). Because I am only a java developer and not an eclipse developer I do not know which component causes the problem when a error log entry is created. I assumed that eclipse can handle that (as I said I used the "report as bug" feature). Thanks for your understanding.
Could you please check your .log file in the .metadata folder of your eclipse installation. You might have more details there.
Hello, meanwhile I cleared the error log. There is an exception that might be related to the one I reported, but I assume that it is not. java.lang.NullPointerException at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTInstructionCompiler.visit(ASTInstructionCompiler.java:3175) 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:504) 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.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:2756) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Moving to JDT/Debug for comments.
The NPE looks remarkably similar to the other bug you filed (bug 282548). It would be good if you could reproduce the ArrayIndexOutOfBoundsException and provide the stack trace for us.
*** This bug has been marked as a duplicate of bug 277574 ***
