Summary: | NullPointerException at org.eclipse.jdt.internal.compiler.ast.QualifiedAllocationExpression.resolveType(QualifiedAllocationExpression.java:225) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Francis ANDRE <francis.andre.kampbell> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.1 | ||
Target Milestone: | 2.1 M5 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Francis ANDRE
2003-01-27 08:01:11 EST
Which build are you running ? Any testcase to reproduce ? Also, are you running Eclipse on IBM JRE 1.3.1 ? The stack trace below shouldn't occur if it comes from 20030122, unless the VM has a bug (the binding couldn't be null there, and even if it was, it should have failed a couple lines above). if ((this.binding = scope.getConstructor(...)).isValidBinding()) { ... } else { if (this.binding.declaringClass == null) // NPE HERE !? this.binding.declaringClass = (ReferenceBinding) receiverType; scope.problemReporter().invalidConstructor(this, this.binding); return receiverType; } Hello I am running Eclipse 2.1 Build id: 200212181304 with the Sun JDK 1.4.1_02. I was not able to reproduce or reduce the scope of such case until now. I will check again soon. Regards Thanks for clarification, then the offending line is: if (!receiverType.canBeInstantiated()) { will investigate. Reproduced: public class X { class Y {} public static void main(String[] arguments) { int i = 0; i.new Y(); } } Fixed Verified. Closed in Eclipse M5 |