Bug 85095 - NPE from Bindings.isEqualMethod
Summary: NPE from Bindings.isEqualMethod
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
: 90511 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-12 19:45 EST by Brock Janiczak CLA
Modified: 2009-08-30 02:08 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 Brock Janiczak CLA 2005-02-12 19:45:54 EST 
Version: 3.1.0
Build id: I20050209-0800

I found the following NullPointerException in my eclipse log.  There was no
error dialog and it didn't seem to stop anything working.  Sorry, no steps to
reproduce.

java.lang.NullPointerException
    at org.eclipse.jdt.internal.corext.dom.Bindings.isEqualMethod(Bindings.java:692)
    at
org.eclipse.jdt.internal.corext.dom.Bindings.findMethodInType(Bindings.java:348)
    at
org.eclipse.jdt.internal.corext.dom.Bindings.findOverriddenMethodInType(Bindings.java:386)
    at
org.eclipse.jdt.internal.corext.dom.Bindings.findOverriddenMethodInHierarchy(Bindings.java:496)
    at
org.eclipse.jdt.internal.corext.dom.Bindings.findMethodDefininition(Bindings.java:525)
    at
org.eclipse.jdt.internal.ui.javaeditor.OverrideIndicatorManager$1.visit(OverrideIndicatorManager.java:183)
    at
org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:488)
    at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
    at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2520)
    at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:486)
    at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
    at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2520)
    at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:291)
    at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2450)
    at
org.eclipse.jdt.internal.ui.javaeditor.OverrideIndicatorManager.updateAnnotations(OverrideIndicatorManager.java:176)
    at
org.eclipse.jdt.internal.ui.javaeditor.OverrideIndicatorManager.reconciled(OverrideIndicatorManager.java:255)
    at
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.reconciled(CompilationUnitEditor.java:1756)
    at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:121)
    at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:133)
    at
org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.reconcile(CompositeReconcilingStrategy.java:86)
    at
org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.reconcile(JavaCompositeReconcilingStrategy.java:94)
    at
org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:75)
    at
org.eclipse.jdt.internal.ui.text.JavaReconciler.process(JavaReconciler.java:318)
    at
org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:204)
Comment 1 Olivier Thomann CLA 2005-02-13 11:43:15 EST 
Move to JDT/UI
Comment 2 Martin Aeschlimann CLA 2005-02-14 06:23:52 EST 
Need a reproducible case.
The NPE means that a method binding gave back an array of parameter types that
contained a 'null'. Moving to jdt.core
Comment 3 Frederic Fusier CLA 2005-06-08 06:16:09 EDT 
*** Bug 90511 has been marked as a duplicate of this bug. ***
Comment 4 John Arthorne CLA 2005-07-05 11:53:26 EDT 
I got this again in the 3.1 final release.  I cannot consistently reproduce, but
here is what I was doing:

There are two related methods:

Resource.checkExists(int, boolean)
Resource.checkAccessible(int)

Elsewhere, I had a code reference to checkExists (Container.java line 181):

  checkExists(flags, true);

I changed the method name like this:

  checkAccessible(flags, true);

I realized the parameters were wrong, so I hit Ctrl+O twice to obtain a list of
all methods available on that type.  I then removed the boolean argument to
correct my error. As I was typing my correction, the error occurred.
Comment 5 Olivier Thomann CLA 2005-07-05 14:25:53 EDT 
I cannot reproduce.
Comment 6 Olivier Thomann CLA 2006-01-17 14:50:32 EST 
Closing as REMIND.
Please reopen if a test case can be provided
Comment 7 Denis Roy CLA 2009-08-30 02:08:41 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.