Bug 78651 - [1.5][compiler] NPE in createParameterizedType
Summary: [1.5][compiler] NPE in createParameterizedType
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2004-11-15 14:19 EST by Bart Geraci CLA
Modified: 2009-08-30 02:07 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Geraci CLA 2004-11-15 14:19:22 EST
Version 3.1.0
Build: 200411101000
Windows 2000

Compiling a file, I get "Internal compiler error" due to an NPE. 
Here's the stack trace:

!ENTRY org.eclipse.core.runtime 4 2 2004-11-15 13:13:27.968
!MESSAGE An internal error occurred during: "Java AST creation".
!STACK 0
java.lang.NullPointerException
	at
org.eclipse.jdt.internal.compiler.lookup.Scope.createParameterizedType(Scope.java:376)
	at
org.eclipse.jdt.internal.compiler.lookup.Scope.leastContainingInvocation(Scope.java:2531)
	at org.eclipse.jdt.internal.compiler.lookup.Scope.lowerUpperBound(Scope.java:2607)
	at
org.eclipse.jdt.internal.compiler.lookup.Scope.leastContainingTypeArgument(Scope.java:2597)
	at
org.eclipse.jdt.internal.compiler.lookup.Scope.leastContainingInvocation(Scope.java:2523)
	at org.eclipse.jdt.internal.compiler.lookup.Scope.lowerUpperBound(Scope.java:2607)
	at
org.eclipse.jdt.internal.compiler.lookup.ParameterizedGenericMethodBinding.computeCompatibleMethod(ParameterizedGenericMethodBinding.java:133)
	at
org.eclipse.jdt.internal.compiler.lookup.Scope.computeCompatibleMethod(Scope.java:231)
	at
org.eclipse.jdt.internal.compiler.lookup.Scope.computeCompatibleMethod(Scope.java:204)
	at org.eclipse.jdt.internal.compiler.lookup.Scope.findMethod(Scope.java:929)
	at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod(Scope.java:1951)
	at
org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:292)
	at org.eclipse.jdt.internal.compiler.ast.Expression.resolve(Expression.java:688)
	at
org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:400)
	at
org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:147)
	at
org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:378)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:985)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1034)
	at
org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:280)
	at
org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:651)
	at
org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:442)
	at org.eclipse.jdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:722)
	at org.eclipse.jdt.core.dom.ASTParser.createAST(ASTParser.java:574)
	at
org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.createAST(ASTProvider.java:563)
	at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST(ASTProvider.java:492)
	at
org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$PartListenerGroup.calculateASTandInform(SelectionListenerWithASTManager.java:165)
	at
org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$3.run(SelectionListenerWithASTManager.java:142)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Comment 1 Philipe Mulet CLA 2004-11-15 15:03:14 EST
Any steps to reproduce ?
Comment 2 Philipe Mulet CLA 2004-11-16 07:45:49 EST
Could only occur if null argument was provided. However, sender checks for
presence of null arguments already.

Need steps to reproduce, then pls reopen.
Comment 3 Bart Geraci CLA 2004-11-16 14:18:32 EST
Since I reported it, I've tried to reproduce the error, but to no avail. 
It's working okay now.
Comment 4 Philipe Mulet CLA 2004-11-16 15:44:20 EST
There were substantial changes recently in this area, so behavior could have
disappeared... but would be good to reproduce since usually these never go away
for free <g>.

Comment 5 Frederic Fusier CLA 2005-02-17 10:04:11 EST
Closing as never reproduced in a long time
Comment 6 Denis Roy CLA 2009-08-30 02:07:22 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.