Summary: | NPE from Bindings.isEqualMethod | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Brock Janiczak <brockj> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | john.arthorne |
Version: | 3.1 | Keywords: | needinfo |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Brock Janiczak
2005-02-12 19:45:54 EST
Move to JDT/UI 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 *** Bug 90511 has been marked as a duplicate of this bug. *** 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. I cannot reproduce. Closing as REMIND. Please reopen if a test case can be provided As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |