This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 250511 - NullPointerException at org.netbeans.modules.java.source.PostFlowAnalysis.visitMethodDef
Summary: NullPointerException at org.netbeans.modules.java.source.PostFlowAnalysis.vis...
Status: RESOLVED DUPLICATE of bug 249472
Alias: None
Product: java
Classification: Unclassified
Component: Compiler (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-19 02:16 UTC by Exceptions Reporter
Modified: 2015-02-27 10:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 215511


Attachments
stacktrace (4.87 KB, text/plain)
2015-02-19 02:16 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2015-02-19 02:16:16 UTC
This bug was originally marked as duplicate of bug 219206, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.21-b01, Java(TM) SE Runtime Environment, 1.7.0_21-b11
OS: Windows 7

User Comments:
GUEST: Unknown




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.modules.java.source.PostFlowAnalysis.visitMethodDef(PostFlowAnalysis.java:171)
   at com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:784)
   at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:49)
   at org.netbeans.modules.java.source.PostFlowAnalysis.scan(PostFlowAnalysis.java:132)
   at com.sun.tools.javac.tree.TreeScanner.scan(TreeScanner.java:57)
   at com.sun.tools.javac.tree.TreeScanner.visitClassDef(TreeScanner.java:80)
Comment 1 Exceptions Reporter 2015-02-19 02:16:18 UTC
Created attachment 152068 [details]
stacktrace
Comment 2 Dusan Balek 2015-02-27 10:06:35 UTC
Already fixed.

*** This bug has been marked as a duplicate of bug 249472 ***