Community
Participate
Working Groups
The following error was reported via the automated error reporting: The user provided the following details for this error report: code: 0 plugin: org.eclipse.jdt.ui_3.10.100.v20141027-2358 message: Error in JDT Core during AST creation fingerprint: ede991a9 exception class: java.lang.NullPointerException exception message: - number of children: 0 java.lang.NullPointerException: null at org.eclipse.jdt.internal.compiler.lookup.ParameterizedGenericMethodBinding.computeCompatibleMethod18(ParameterizedGenericMethodBinding.java:198) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedGenericMethodBinding.computeCompatibleMethod(ParameterizedGenericMethodBinding.java:81) at org.eclipse.jdt.internal.compiler.lookup.Scope.computeCompatibleMethod(Scope.java:730) at org.eclipse.jdt.internal.compiler.lookup.Scope.computeCompatibleMethod(Scope.java:687) at org.eclipse.jdt.internal.compiler.lookup.Scope.findMethod0(Scope.java:1619) at org.eclipse.jdt.internal.compiler.lookup.Scope.findMethod(Scope.java:1520) at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod(Scope.java:2791) at org.eclipse.jdt.internal.compiler.ast.JavadocFieldReference.internalResolveType(JavadocFieldReference.java:86) at org.eclipse.jdt.internal.compiler.ast.JavadocFieldReference.resolveType(JavadocFieldReference.java:132) at org.eclipse.jdt.internal.compiler.ast.Javadoc.resolveReference(Javadoc.java:389) at org.eclipse.jdt.internal.compiler.ast.Javadoc.resolve(Javadoc.java:240) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1214) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1320) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:590) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:1204) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:689) at org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:1183) at org.eclipse.jdt.core.dom.ASTParser.createAST(ASTParser.java:809) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider$1.run(ASTProvider.java:544) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.createAST(ASTProvider.java:537) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST(ASTProvider.java:480) at org.eclipse.jdt.ui.SharedASTProvider.getAST(SharedASTProvider.java:128) at com.codetrails.connect.codesearch.rcp.FullIndexingJob.foreachCompilationUnit(FullIndexingJob.java:154) at com.codetrails.connect.codesearch.rcp.FullIndexingJob.foreachPackageFragment(FullIndexingJob.java:145) at com.codetrails.connect.codesearch.rcp.FullIndexingJob.foreachPackageFragmentRoot(FullIndexingJob.java:129) at com.codetrails.connect.codesearch.rcp.FullIndexingJob.foreachProject(FullIndexingJob.java:119) at com.codetrails.connect.codesearch.rcp.FullIndexingJob.analyze(FullIndexingJob.java:101) at com.codetrails.connect.codesearch.rcp.FullIndexingJob.run(FullIndexingJob.java:65) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) General Information: reported-by: Marcel Bruch anonymous-id: f8087d7b-9d38-4c73-aeb1-6991603c2a84 eclipse-build-id: 4.5.0.I20141029-2000 eclipse-product: org.eclipse.epp.package.committers.product operating system: MacOSX 10.10.1 (x86_64) - cocoa jre-version: 1.8.0_20-b26 The following plug-ins were present on the execution stack (*): 1. com.codetrails.connect.codesearch.rcp_1.2.16.v20141216-1526-b1073 2. com.codetrails.connect.codesearch_1.2.16.v20141216-1526-b1073 3. org.eclipse.core.jobs_3.6.100.v20140929-1332 4. org.eclipse.core.runtime_3.10.0.v20140724-1132 5. org.eclipse.jdt_3.11.0.v20141029-2000 6. org.eclipse.jdt.core_3.11.0.v20141029-0804 7. org.eclipse.jdt.ui_3.10.100.v20141027-2358 Please note that: * Messages, stacktraces, and nested status objects may be shortened. * Bug fields like status, resolution, and whiteboard are sent back to reporters. * The list of present bundles and their respective versions was calculated by package naming heuristics. This may or may not reflect reality. Please visit http://goo.gl/MWFSff for further details. Thank you for your assistance. Your friendly error-reports-inbox.
Moving to JDT for review. We got this when we indexed a larger Eclipse workspace with Mars M3. Cannot provide the classnames that caused the NPE yet (but maybe soon if the new log messages show up).
*** Bug 455359 has been marked as a duplicate of this bug. ***
Likely a duplicate of bug 451418 which was fixed for M4. Marcel are you saying you can reproduce? If so, can you try M4? TIA