Bug 265795 - NPE Problemreporter
Summary: NPE Problemreporter
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.6 M3   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-23 03:15 EST by Martin Ulmschneider CLA
Modified: 2009-10-26 11:00 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Ulmschneider CLA 2009-02-23 03:15:18 EST 
Build ID: M20080911-1700

Steps To Reproduce:
I unforunately don't have any steps to reproduce. The following Exception appeared in the Problems-View after Eclipse crashed and after cleaning & refreshing the workspace.

Internal compiler error
java.lang.NullPointerException

	at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.missingTypeInConstructor(ProblemReporter.java:4897)

	at org.eclipse.jdt.internal.compiler.ast.ExplicitConstructorCall.resolve(ExplicitConstructorCall.java:393)

	at org.eclipse.jdt.internal.compiler.ast.ConstructorDeclaration.resolveStatements(ConstructorDeclaration.java:465)

	at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:403)

	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1096)

	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1184)

	at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:535)

	at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:743)

	at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:137)

	at java.lang.Thread.run(Thread.java:619)

Internal compiler error
java.lang.NullPointerException

	at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.missingTypeInConstructor(ProblemReporter.java:4897)

	at org.eclipse.jdt.internal.compiler.ast.ExplicitConstructorCall.resolve(ExplicitConstructorCall.java:393)

	at org.eclipse.jdt.internal.compiler.ast.ConstructorDeclaration.resolveStatements(ConstructorDeclaration.java:465)

	at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:403)

	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1096)

	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1184)

	at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:535)

	at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:743)

	at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:137)

	at java.lang.Thread.run(Thread.java:619)

More information:

I have no idea what Infomation might be helpful in this case. If you need anything specific, please ask.

Compiler-compliance setting was set to 1.6
Comment 1 Martin Ulmschneider CLA 2009-02-23 03:28:37 EST 
deleting the content of the $workspace\.metadata\.plugins\org.eclipse.jdt.core folder solved the problem.
Comment 2 Olivier Thomann CLA 2009-10-06 11:08:28 EDT 
Closing as WORKSFORME.
Next time keep the data you deleted. This could help us to reproduce.
Comment 3 Frederic Fusier CLA 2009-10-26 11:00:12 EDT 
Verified for 3.6M3