Community
Participate
Working Groups
Created attachment 269857 [details] Sources which occur the bug Error: Exception in thread "main" java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.ast.MessageSend.analyseCode(MessageSend.java:141) at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.analyseCode(MethodDeclaration.java:125) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.internalAnalyseCode(TypeDeclaration.java:739) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.analyseCode(TypeDeclaration.java:263) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.analyseCode(CompilationUnitDeclaration.java:118) at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:873) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:1006) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:630) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:993) at test.Main2.main(Main2.java:56)
Created attachment 269858 [details] Use it to build ASTs
We fixed several similar exceptions over time :-/ I can reproduce using that attached sources. Before the crash several compile errors are reported, one of them being: ---------- 1. ERROR in /tmp/JDT_Bug/ru/mail/mailbox/cmd/server/TornadoUploadRequest.java (at line 4) public class TornadoUploadRequest extends NetworkCommand<Params> { ^^^^^^ Params cannot be resolved to a type ---------- If I add an empty interface Params, then the NPE no longer occurs. Does this correspond to your observation, or do you see NPE also in error-free code?
No, I don't see. When I change Params to Void, NPE is no longer appears
Thanks for confirming. Will need to protect against unresolved type anyway, tentatively scheduling for 4.8.
bulk move out of 4.8
Hi, any changes? Doesn't seem to be fixed, but last comment was more than a year ago
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.