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.
Build: NetBeans IDE Dev (Build 201301240001) VM: Java HotSpot(TM) 64-Bit Server VM, 23.6-b04, Java(TM) SE Runtime Environment, 1.7.0_10-b18 OS: Windows 7 User Comments: GUEST: Resolving conflicts of a Java source code Stacktrace: java.lang.NullPointerException at com.sun.tools.javac.jvm.Code.emitop1w(Code.java:939) at com.sun.tools.javac.jvm.Items$LocalItem.load(Items.java:392) at com.sun.tools.javac.jvm.Gen.visitBinary(Gen.java:1959) at com.sun.tools.javac.tree.JCTree$JCBinary.accept(JCTree.java:1568) at com.sun.tools.javac.jvm.Gen.genExpr(Gen.java:840) at com.sun.tools.javac.jvm.Gen.genCond(Gen.java:820)
Created attachment 131273 [details] stacktrace
Created attachment 146541 [details] stacktrace build project in console
No report except the last one (#719925) are relevant to 8.0 release. Possibly #657465 might be related. Both #657465 and #719925 show an error fired up from an annotation processor during enter phase and subsequent compiler failure. The cause might be a missing symbol (because of unfinished compilation phase), or an invalid local index (= a compiler implementation error). The VarSymbol.adr is written by newLocal in code generator, but also by Flow definitive assignment analyzer. If a symbol's use in code generator would be used before its VarDef is visited, AND it's index from the definitive assignment analysis is high enough - this error could happen. I'm not sure whether/how this can happen though.
*** Bug 187641 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 178299 ***