Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369498

Summary:	NPE in WildcardBinding
Product:	[Eclipse Project] JDT	Reporter:	Peter Larsen <peblpebl>
Component:	Core	Assignee:	Stephan Herrmann <stephan.herrmann>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	amj87.iitr, stephan.herrmann
Version:	3.7.1
Target Milestone:	4.14
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Peter Larsen

2012-01-24 07:04:46 EST

Build Identifier: M20110909-1335

!SESSION 2012-01-18 20:02:49.576 -----------------------------------------------
eclipse.buildId=M20110909-1335
java.version=1.6.0_21
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=da_DK
Command-line arguments:  -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.core.resources 2 10035 2012-01-18 20:03:10.421
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.mylyn.tasks.ui 2 0 2012-01-18 20:03:17.749
!MESSAGE No search provider was registed. Tasks search is not available.

!ENTRY org.eclipse.core.resources 4 2 2012-01-18 20:04:13.862
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
	at org.eclipse.jdt.internal.compiler.lookup.WildcardBinding.initialize(WildcardBinding.java:436)
	at org.eclipse.jdt.internal.compiler.lookup.WildcardBinding.<init>(WildcardBinding.java:45)
	at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createWildcard(LookupEnvironment.java:1041)
	at org.eclipse.jdt.internal.compiler.lookup.Scope.lowerUpperBound(Scope.java:3357)
	at org.eclipse.jdt.internal.compiler.lookup.Scope.lowerUpperBound(Scope.java:3288)
	at org.eclipse.jdt.internal.compiler.ast.ConditionalExpression.resolveType(ConditionalExpression.java:537)
	at org.eclipse.jdt.internal.compiler.ast.Assignment.resolveType(Assignment.java:150)
	at org.eclipse.jdt.internal.compiler.ast.Expression.resolve(Expression.java:947)
	at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:463)
	at org.eclipse.jdt.internal.compiler.ast.ConstructorDeclaration.resolveStatements(ConstructorDeclaration.java:515)
	at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:422)
	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1148)
	at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1258)
	at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:539)
	at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:763)
	at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:137)
	at java.lang.Thread.run(Unknown Source)


Reproducible: Couldn't Reproduce

Steps to Reproduce:
Just found in the .log while looking for some other error.
I did not notice anything really odd at the time.

Comment 1 Ayushman Jain

2012-01-24 08:05:53 EST

The NPE is on line 
this.tagBits |= someOtherBound.tagBits & TagBits.ContainsNestedTypeReferences
Seems like the binding for one of the bounds turned out to be null.

Comment 2 Ayushman Jain

2012-01-24 08:06:32 EST

The build in comment 0 corresponds to 3.7.1

Comment 3 Eclipse Genie

2019-12-07 14:20:13 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Stephan Herrmann

2019-12-07 15:08:12 EST

I don't see anything we could do with just that exception trace.