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 170220 - NullPointerException at com.sun.tools.javac.jvm.Code.emitop1w
Summary: NullPointerException at com.sun.tools.javac.jvm.Code.emitop1w
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Compiler (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Dusan Balek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-11 17:10 UTC by Oleg Khokhlov
Modified: 2009-09-03 12:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 152194

Attachments
stacktrace (4.53 KB, text/plain)
2009-08-11 17:10 UTC, Oleg Khokhlov 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Khokhlov 2009-08-11 17:10:32 UTC 
Build: NetBeans IDE Dev (Build 200908100201)
VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Windows XP, 5.1, x86

User Comments:
ovk: adding JDK



Stacktrace: 
java.lang.NullPointerException
        at com.sun.tools.javac.jvm.Code.emitop1w(Code.java:921)
        at com.sun.tools.javac.jvm.Items$LocalItem.load(Items.java:392)
        at com.sun.tools.javac.jvm.Gen.visitSelect(Gen.java:2155)
        at com.sun.tools.javac.tree.JCTree$JCFieldAccess.accept(JCTree.java:1655)
        at com.sun.tools.javac.jvm.Gen.genExpr(Gen.java:835)
        at com.sun.tools.javac.jvm.Gen.visitBinary(Gen.java:1945)
Comment 1 Oleg Khokhlov 2009-08-11 17:10:40 UTC 
Created attachment 86112 [details]
stacktrace
Comment 2 Dusan Balek 2009-08-19 09:53:00 UTC 
Are you able to reproduce the issue on your sources?
Comment 3 Oleg Khokhlov 2009-08-27 16:16:00 UTC 
can't reproduce with latest build
Comment 4 Peter Pis 2009-09-03 12:52:59 UTC 
Closing as WORKSFORME. In a case you will face to this problem again, please reopen the issue and provide further details.