| Summary: | [change method signature] NPE in ConstructorReferenceFinder | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | garry star <gstar42> |
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | markus.kell.r, martinae |
| Version: | 3.2.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
garry star
Move to JDT/UI This is a very strange stack trace.
NPE on this line ((AbstractTypeDeclaration) node.getParent()).getNameProperty().equals(node.getLocationInParent())) {
but node and node.getParent are guaranteed to be not null. And getNameProperty can also never return null.
We need some code example that can reproduce this. Markus, any ideas?
Garry, can you reproduce this problem? It looks like you were trying to change the signature of a constructor, but I could not come up with a test case that fails. Any hints about the circumstances would be helpful. (In reply to comment #2) This is against 3.2.2, not HEAD. In 3.2.2, the NPE is one line up, at if (node.getParent() instanceof AbstractTypeDeclaration The node from ASTNodeSearchUtil.getAstNode(searchResult, cuNode) seems to be null, which indicates a problem with search result ranges. 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. |